mitre-attack / mitre-attack/attack-workbench-frontend
[REQUEST] Feature to identify the ATT&CK Collection an Object is part of
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
Users currently cannot easily identify which ATT&CK collection (ATT&CK release version) a specific object belongs to, making it more difficult to track its version history.
Solution:
Develop a feature that clearly displays the ATT&CK collection or release version associated with each object.
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 locating the Angular views that display ATT&CK objects and the data path supplying collection or release metadata. Determine how an object is associated with an ATT&CK collection, then define where that association should appear in the interface. Done means each object clearly displays its associated collection or release version and the behavior is covered by appropriate tests.
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
- Needs clarification
- Newbie friendliness
- 32/100