Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52161

[API token] Manage Legacy API Token usage UX date since use labeling should be restructured

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None
    • Jenkins 2.130

      User Id User full name Token name Days since creation
      # of use
      Days since last use Fresh token? Recent token?
      jenkins Jenkins Account Legacy Token 0 155 0 ✅ 
      hudson Hudson Account Legacy Token 0 0 0 ⚠️ ⚠️ 
      other Account Legacy Token 1 173 0 ⚠️ ✅ 

      I've sent a PR to address the easy part of the text.

      But, the Days column is really confusing, in part because there's no distinction between tokens that were created before migration and tokens created today (some day, potentially long..., after migration)

      For the case where there hasn't been a use, e.g., hudson above, the answer should be Unknown or something similar. For the case where the token was used today, e.g., jenkins above.

      As is, both of those cases appear as "0", but they are very different and should not be rendered in the same manner.

       

          [JENKINS-52161] [API token] Manage Legacy API Token usage UX date since use labeling should be restructured

          Josh Soref created issue -
          Josh Soref made changes -
          Description Original: ||User Id||User full name||Token name||Days since creation||
          # of use||Days since last use||Fresh token?||Recent token?||
          |jenkins|Jenkins Account|Legacy Token|0|155|0|✅|✅ |
          |hudson|Hudson Account|Legacy Token|0|0|0|⚠️|⚠️ |

          I've sent a PR to address the easy part of the text.

          But, the Days column is really confusing.

          A better approach for it is to change the column title to *Last used*.

          For the case where there hasn't been a use, e.g., {{hudson}} above, the answer should be *Unknown* or something similar. For the case where the token was used today, e.g., {{jenkins}} above, the answer should be *Today* (bonus points for rendering *Yesterday*, _x_ *days ago*, _x_ *weeks ago*, etc.).

           

          As is, both of those cases appear as "0", but they are *very* different and should not be rendered in the same manner.
          New: ||User Id||User full name||Token name||Days since creation||\\# of use||Days since last use||Fresh token?||Recent token?||
          |jenkins|Jenkins Account|Legacy Token|0|155|0|✅|✅ |
          |hudson|Hudson Account|Legacy Token|0|0|0|⚠️|⚠️ |

          I've sent a PR to address the easy part of the text.

          But, the Days column is really confusing.

          A better approach for it is to change the column title to *Last used*.

          For the case where there hasn't been a use, e.g., {{hudson}} above, the answer should be *Unknown* or something similar. For the case where the token was used today, e.g., {{jenkins}} above, the answer should be *Today* (bonus points for rendering *Yesterday*, _x_ *days ago*, _x_ *weeks ago*, etc.).

           

          As is, both of those cases appear as "0", but they are *very* different and should not be rendered in the same manner.
          Josh Soref made changes -
          Summary Original: Manage Legacy API Token usage UX date since use labeling should be reworded New: Manage Legacy API Token usage UX date since use labeling should be restructured
          Oleg Nenashev made changes -
          Assignee New: Wadeck Follonier [ wfollonier ]
          Wadeck Follonier made changes -
          Remote Link New: This issue links to "#3524 core, revoke, alt (Web Link)" [ 21106 ]
          Wadeck Follonier made changes -
          Remote Link New: This issue links to "#3519, core, cleanup migration screen (Web Link)" [ 21107 ]
          Wadeck Follonier made changes -
          Link New: This issue relates to JENKINS-32442 [ JENKINS-32442 ]
          Wadeck Follonier made changes -
          Link New: This issue relates to JENKINS-32776 [ JENKINS-32776 ]
          Wadeck Follonier made changes -
          Remote Link New: This issue links to "#3525 core, consider "null" for creation (Web Link)" [ 21108 ]
          Wadeck Follonier made changes -
          Link New: This issue relates to JENKINS-52182 [ JENKINS-52182 ]
          Wadeck Follonier made changes -
          Link New: This issue relates to JENKINS-52183 [ JENKINS-52183 ]

            wfollonier Wadeck Follonier
            jsoref Josh Soref
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: