Workflow: DM "not approved" must have reasons
Open
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
"Not approved" option is needed and require reasons
Reference FRPA 37(4)Need place for DM to attach reasons for decision when "not approved" selected
Reasons MUST have content if status is "not approved"
Possibly require place for staff to provide draft not-approved reasons
Original discussion was that "not approved" should trigger staff follow up with AH --> check with SME re. if this is still desired
Part of large DM process upgrade from "bare-bones"
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.