Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] v14rc4 - Members uses same approach as Users #16694

Open
warrenbuckley opened this issue May 23, 2024 · 3 comments
Open

[FEATURE] v14rc4 - Members uses same approach as Users #16694

warrenbuckley opened this issue May 23, 2024 · 3 comments

Comments

@warrenbuckley
Copy link
Contributor

Is your feature request related to a problem? Please describe.
I find it unusual that the list of Members is not approached in the same way as Users as I would like to select one or more members to perform an action on a member

Describe the solution you'd like
Make the Members section work in the same or similar way that Users does.

  • Filter by User Groups
  • Filter by Approved/Unapproved
  • Filter by Members who are Locked out
  • Change sort direction
  • Consider different view from table to include grid like members
  • More columns in table view
    • Last Login
    • Member Group/s
    • Approved
  • Select one or more items from table to perform bulk actions
    • Delete, Approve, Unapprove, Assign Member Group/s

Users

image

Members

image

@iOvergaard iOvergaard transferred this issue from umbraco/Umbraco.CMS.Backoffice Jun 27, 2024
Copy link

Hi there @warrenbuckley!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@nielslyngsoe
Copy link
Member

Hi @warrenbuckley

I agree in your reasons and wished solution.

To be realistic, as this is not a bug, it will take sometime before we at HQ will look at this. Until that any PRs aligning on this topic is welcome.

Thanks

Copy link

Hi @warrenbuckley,

We're writing to let you know that we would love some help with this issue. We feel that this issue is ideal to flag for a community member to work on it. Once flagged here, folk looking for issues to work on will know to look at yours. Of course, please feel free work on this yourself ;-). If there are any changes to this status, we'll be sure to let you know.

For more information about issues and states, have a look at this blog post.

Thanks muchly, from your friendly Umbraco GitHub bot :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

3 participants