Actions
User story #12261
closed
User story #12202: Missing information/bad UX in API authorization UI
Add a visual difference between API token kind
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
So that we know if it's a standard token, one linked to an user, a system one, et.
Updated by François ARMAND over 6 years ago
- Translation missing: en.field_tag_list deleted (
Blocking 4.3) - Status changed from New to Rejected
In fact, we just don't want to display user token in that table: #12281
So this tiket is not relevant anymore.
Actions