opensafely-core / opensafely-core/reports
Make the default state "draft" when adding new report
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
Currently users check a box to toggle a report to private (draft):
I think it would be better to have the opposite toggle.
Reasons:
- we will almost always want to look at a new report in draft mode first before publishing it (to sense check, check that layout is as expected etc), so when first added they will almost always need to be draft initially.
- It's better to make a new, untested, report accidentally private than accidentally public
Also:
We could/should also add a checklist of necessary actions required before toggling a report to public, so that it's easy to check they are all completed without having to look for guidance elsewhere. See this document.
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
The issue names no files, tests, or entry points. First locate the report-creation flow and its existing private/draft toggle, then confirm how new report state is set. Done means new reports start as draft, with the additional pre-publication checklist clarified and implemented if that part is in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100