nextcloud / nextcloud/approval
Suggestion for a generally clearer design in the settings
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 10
- Avg merge
- 20m
- Merged PRs (30d)
- 4
Description
Suggestion for a generally clearer design in the settings: If several approval procedures are created in the settings, especially chained approval procedures, it quickly becomes confusing. If you imagine that there are several such processes in a medium-sized company, you quickly end up in chaos. Could this interface be rethought? This needs to become more powerful. All in all, I think the app is very important. A good idea. This was missing in Nextcloud and is especially important for companies. It would be great if a solution could be found, possibly directly with Nextcloud, to speed up the development process. I have been wondering for a while that this is not perceived accordingly.
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
No file, test, or entry point is named. Start by reviewing the settings UI for approval procedures and turn the broad redesign request into a concrete scope with acceptance criteria for multiple and chained procedures; done should be a specific agreed interface change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100