mitre-attack / mitre-attack/attack-workbench-frontend
[REQUEST] Improve Accessibility of Workflow Status Change Options
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
Currently, changing the workflow status of an object requires going through the toolbar's settings dropdown, making this action less visible and require multiple clicks to complete. To improve usability and streamline the release workflow, the workflow status controls should be moved to a more accessible location, such as a dedicated toolbar group with individual buttons for each status or a status indicator with a dropdown directly in the main toolbar.
Note: Consideration is needed in how to handle validation requirements for workflow status changes, as only objects that pass full backend validation should be allowed to move to "Awaiting Review" or "Reviewed" (See api#405)
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 tracing the workflow status controls in the toolbar's settings dropdown and review api#405 for the validation requirements. Determine the approved toolbar presentation and ensure that moving objects to "Awaiting Review" or "Reviewed" is limited to objects passing full backend validation; the work is done when the controls are more visible and the restrictions are enforced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100