opensafely-core / opensafely-core/reports
Clearly mark draft reports as such
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
Draft reports can only be viewed by people who are logged in. However for practical reasons we're circulating the URLs and a readonly username/password for this quite widely -- it's possible that these will get as far as people who aren't familiar with the system and may not know that they are looking at a draft report. If that happens the results may be then further propagated when they are not completely reliable.
To reduce the impact when this happens, we should clearly mark draft reports as such in the UI. This already happens to a certain extent -- in the menu on the left the report name is annotated as draft; but when you're looking at an individual report there is no way of knowing it's draft.
Contributor guide
No contributing guide indexed for this repository
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
Find the individual-report UI and compare it with the left menu, where draft reports are already annotated. Add a clear draft indicator to the individual report view, then verify that draft reports visibly identify themselves while being viewed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100