Item | Discussion |
---|
Evaluation report flow review | https://govstack-global.atlassian.net/wiki/spaces/GH/whiteboard/300449806 |
Designs review | https://www.figma.com/file/9XudBIl7YAt3aH1nMBoO4L/govstack?type=design&node-id=1629-5341&mode=design&t=Vjk2nPjbWXddeRoI-0 |
Clarify requirements | How do we want to add this functionality to the current testing web app https://testing.govstack.global/ ? And should we do it? What about authentication? Statuses - do we need more statuses for reviewers? What statuses exactly do we need? Draft In review Published Rejected / Not passed ?
Date - how should we indicate different evaluation dates in the software? Compliance Level - should we add tooltips to explain what each compliance level means? Saving draft (can be accessed again to finish submitting) - what flow of saving?
|
Identify any potential gaps | What happens if a person submits a form knowing that it does not fulfill a compliance level. Do we still show it? What do we call that state? "Not passed"? What happens if a person submits an empty form? I suggest status "n/a" Do we allow comments for each requirement? My impression so far was that people needed to explain why, why not or why partially something it met
|
Next steps | |