Opened 4 years ago
Last modified 4 years ago
#51942 new enhancement
Application Password pagination
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | 5.6 |
| Component: | Application Passwords | Keywords: | needs-design-feedback |
| Focuses: | ui, administration | Cc: |
Description
Currently, the Application Password entries are stored on one page.
Not sure how many entries are we expecting, but it might be worth using pagination here for better UX.
Attachments (1)
.png){kind=link}
.png){kind=link}
Change History (11)
#1
@
4 years ago
- Milestone changed from Awaiting Review to 5.7
Hello @Boniu91,
Thank you for identifying this during today's 5.6 testing scrub as well as creating this ticket.
Moving into 5.7 per @TimothyBlynJacobs comment on Slack:
We don’t enforce unique names and pagination is not currently implemented. Both are 5.7 things. Would be great to open separate tickets for each.
#2
@
4 years ago
Related: #51899
Maybe we could move the Application Passwords table to a separate screen, for consistency with other list tables?
This ticket was mentioned in Slack in #core-restapi by hellofromtonya. View the logs.
4 years ago
#4
@
4 years ago
- Keywords needs-design-feedback added
Timothy suggested getting design feedback for Sergey's idea of moving Application Passwords table to a separate screen and using list table (for consistency).
This ticket was mentioned in Slack in #design by hellofromtonya. View the logs.
4 years ago
This ticket was mentioned in Slack in #design by chaion07. View the logs.
4 years ago
#7
@
4 years ago
From my design perspective, I think the pagination will create more hassle for users (as of now), unless the Application Passwords page is separated to a single page for all users.
#8
@
4 years ago
After reviewing the ticket in design triage, we have questions.
Realistically, how many passwords will a regular user have? Think here that sites with 20+ users are not the majority of websites, although a good use case.
Being this a new feature, we suggest that is better to see which use cases show up before suggesting that a feature be moved to another place. Moving things around without feedback.
#10
@
4 years ago
- Milestone changed from 5.7 to Awaiting Review
Moving this ticket back to Awaiting Review. Why?
- Redesign effort is underway in #51899
- Need more information from users to determine if pagination would improve the workflow and UX
If any maintainer or committer feels this can be resolved in time, or wishes to assume ownership during a specific cycle, feel free to update the milestone accordingly.
Screenshot