mitre-attack / mitre-attack/attack-workbench-frontend
[REQUEST] Add Option to Generate a Changelog for Collections
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
Workbench currently lacks an option to automatically generate a changelog document for collections. While changes to ATT&CK objects are visible in Workbench, they are not compiled into a formatted changelog similar to the release notes on the ATT&CK website. This makes the process of creating a changelog more tedious and time consuming, even though the required information is already available in Workbench.
Solution:
Add a feature to automatically generate a changelog for collections based on the current changes in ATT&CK objects. The changelog should be editable, allowing users to add descriptions or modify entries before it is marked as a release.
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 tracing the Workbench collection-change view and the existing release-note workflow described in the issue, then identify where ATT&CK object changes are assembled. The work is done when a collection changelog can be generated, edited with descriptions or modified entries, and marked as a release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100