Marking Teams as favorite
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 68
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 60
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
Which Nextcloud Version are you currently using: 31
Is your feature request related to a problem? Please describe.
Working a lot with Teams and Collectives, the Teams list in the left sidebar in the contacts grows quickly. Especially since it's only possible to create one Collective per Team. This makes it harder to find the relevant Teams quickly (those actually used as overview over a project e.g. vs. those just there because a Collective has been created)
Describe the solution you'd like
Marking a Team as favorite moves it to the top of the list. In addition, this happens on the dashboard widget, too. It would be even nicer if there was a widget only showing the favorites.
Describe alternatives you've considered
Sorting Teams in the left sidebar would also work, however this hasn't any effect on the Dashboard widget.
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the feature request as the starting point and trace how Teams are rendered in the left sidebar and the dashboard widget. Clarify whether favoriting should affect both lists and whether a favorites-only widget is in scope; done means the requested favorite ordering behavior is implemented consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100