mitre-attack / mitre-attack/attack-workbench-frontend
Require Team Lead Approval for Objects in Collections
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
Currently, objects can be added to a collection (bundle) without prior approval, which may result in unreviewed or inaccurate content being included.
Solution:
Implement a feature that prevents objects from being added to a collection unless they have been reviewed and approved by a Team Lead
Potential Implementations:
- Add a validation step that blocks unapproved objects from being included in a collection.
- Add notification on which objects require approval when users are attempting to add unapproved objects.
- Include a "Pending Approval" section in the collection builder to track objects awaiting Team Lead review.
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
The issue does not name files or tests; start by locating the collection builder's object-add flow and the existing Team Lead approval state. Define the approval behavior and notification or pending-approval presentation before implementing it; done means unapproved objects cannot be added to collections and users can identify what requires review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100