• Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None

      The idea is simple, splitting the different user properties into categories, as it was done for the Global Configuration pages.

      An interesting effect if we are doing this: the security category can be restricted further, for example by reasking the password. This kind of requirement is not necessary when the user wants to change his description or his default view.

      By splitting the /configure page, we will need to deprecate the previously used doConfigSubmit from the user, to have one per category.

          [JENKINS-69869] Categorize the user properties

          Wadeck Follonier created issue -
          Wadeck Follonier made changes -
          Link New: This issue relates to JENKINS-69853 [ JENKINS-69853 ]
          Wadeck Follonier made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Wadeck Follonier made changes -
          Remote Link New: This issue links to "#7268 in core (Web Link)" [ 28278 ]
          Wadeck Follonier made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]
          Wadeck Follonier made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Mark Waite made changes -
          Released As New: 2.468
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Fixed but Unreleased [ 10203 ]
          Mark Waite made changes -
          Status Original: Fixed but Unreleased [ 10203 ] New: Resolved [ 5 ]
          Mark Waite made changes -
          Released As Original: 2.468 New: 2.468 https://www.jenkins.io/changelog-stable/2.479.1/

            wfollonier Wadeck Follonier
            wfollonier Wadeck Follonier
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: