Review clarity surrounding web UI "retry" versus refresh
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
This comes up often enough there is perhaps some room for improvement so that people know what to do:
E.g. https://help.nextcloud.com/t/updating-always-fails-during-the-backup-step/175806/11?u=jtr
- Clarity of instructions in app
- Clarity of Updater documentation
- Anything else related to this
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
Start by reviewing the linked help.nextcloud.com report and the updater's web UI instructions for retry versus refresh. Then inspect the updater documentation and related in-app wording; done means the required action is unambiguous in both places and any other relevant guidance is identified.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, frontend
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100