-
Task
-
Resolution: Fixed
-
Minor
-
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.
- relates to
-
JENKINS-52182 [API Token] Improve the "fresh" / "recent" token column
-
- Open
-
-
JENKINS-52183 [API Token] Replace number of days by Today, Yesteday, x weeks ago, etc.
-
- Open
-
-
JENKINS-32776 Jenkins shouldn't store API tokens in a recoverable format
-
- Resolved
-
-
JENKINS-32442 Disable Jenkins API tokens by default
-
- Resolved
-
- links to
[JENKINS-52161] [API token] Manage Legacy API Token usage UX date since use labeling should be restructured
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. |
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 |
Assignee | New: Wadeck Follonier [ wfollonier ] |
Remote Link | New: This issue links to "#3524 core, revoke, alt (Web Link)" [ 21106 ] |
Remote Link | New: This issue links to "#3519, core, cleanup migration screen (Web Link)" [ 21107 ] |
Link |
New:
This issue relates to |
Link |
New:
This issue relates to |
Remote Link | New: This issue links to "#3525 core, consider "null" for creation (Web Link)" [ 21108 ] |
wfollonier PTAL