Project

General

Profile

Actions

User story #12202

closed

Missing information/bad UX in API authorization UI

Added by François ARMAND about 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
UX impact:
Suggestion strength:
Require - I need this to use Rudder as I intend
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Name check:
Fix check:
Regression:

Description

We need to add the following information before finale:

  • for each account, we nned to see in the grid its authorization type (read only, etc). It could be either a tag (alike [audit] etc for directives) or a dedicated column (allowing to sort by authz kind). In any case, the table would be filterable by authz type,

And correct the following points:

  • bad css for previous/next grid buttons
  • Account name and Expiration date content are not vertically centered
  • Table is cut at the bottom
  • validity expiration behave unconsistantly:
    • on creation, we should have the current date + one month pre-filled (defautl value)
    • we should have a checkbox for expiration date to be able to disable it (for now, impossible to disable it if enabled)

Subtasks 5 (0 open5 closed)

Bug #12224: Broken layout on API accounts page in 4.3RejectedActions
User story #12260: Error on first save after api token editReleasedVincent MEMBRÉActions
Bug #12333: Display missing information in api account modified diffRejectedVincent MEMBRÉActions
User story #12261: Add a visual difference between API token kindRejectedActions
User story #12281: Filter out non-standard API token in API token management pageReleasedVincent MEMBRÉActions

Related issues 1 (0 open1 closed)

Related to Rudder - User story #11946: Interface to manage API account authorizationReleasedVincent MEMBRÉActions
Actions

Also available in: Atom PDF