mitre-attack / mitre-attack/attack-workbench-frontend
[REQUEST] Wire `into_candidates` into release track config
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
The API supports a newer release track promotion policy option:
promotion_conflicts: {
into_candidates
candidates_to_staged
staged_to_members
}
The frontend currently exposes conflict policies for candidates_to_staged and staged_to_members, but not into_candidates. into_candidates controls what happens when objects being added into Candidates conflict with an existing version already tracked by the release track.
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 frontend release track configuration that exposes the existing candidates_to_staged and staged_to_members conflict policies. Compare those controls with the API's promotion_conflicts option for into_candidates, then verify that the new policy can be configured and that the three conflict policies are presented consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100