NASA-AMMOS / NASA-AMMOS/plandev
"This Plan brought to you by files X, Y, and Z" Traceability in the UI
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
There are related ideas in https://github.com/NASA-AMMOS/aerie/issues/1318
Describe the feature request
As a planner and plan reviewer, I would like to be looking at a Plan and know what files (especially what file versions) are being used to create the generated elements in the Plan and be able to trace Activities and Resource impacts back to the source files.
It would be nice to have a way to view in the AERIE UI a kind of "this Plan brought to you by files x, y, and z" final credits-like info and follow Parent->Child spawn and Scheduler Goal links back to a source file (if there is one) or other source.
Traceability will be particularly helpful when source files are no longer valid or have changed and all the scheduled descendants need to be wiped out or shifted within a Plan.
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 reading the related discussion in issue #1318 and the traceability requirements described here. The request is complete when the UI can identify the files and file versions behind a Plan and link Activities, Resource impacts, Parent->Child spawns, and Scheduler Goal relationships back to their sources.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100