mitre-attack / mitre-attack/attack-workbench-frontend
[BUG] Exclude existing candidates from the Add Candidates modal
Open
@adpare is already working on this.
Since Aug 14, 2026.
bug
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
On a release track page, the Add Candidates modal currently still shows objects that have already been added as candidates to the release track. Users can select and submit those objects again. The API de-duplicates and ignore the duplicates, but the UI should hide already-added candidates from the available options.
Implementation Note
The StixListConfig already supports an excludeIDs option, which could be leveraged here by populating it with the current release track candidate IDs.
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.
Assessment
This issue has not been assessed yet.