mitre-attack / mitre-attack/attack-workbench-frontend
[REQUEST] Make the workflow for editing/deprecating/deleting relationships more intuitive
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
Specifically on the "Software uses Technique" workflow. It isn't the clearest experience that if a Software no longer uses a Technique that it should be deprecated as opposed to deleted. The Deprecated button is there, and next to it the delete button is grayed out, but then becomes available when you are editing that relationship.
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
Locate the Software uses Technique workflow and inspect how the Deprecated and delete controls behave before and during editing. Compare the current relationship actions and determine how the interface should make deprecating versus deleting clearer. Done means the workflow communicates the distinction intuitively and the controls behave consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100