NASA-AMMOS / NASA-AMMOS/plandev
SEQ IDs are not inherited from parent activity
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
winner
https://jira.jpl.nasa.gov/browse/AERIEQS-273
Moderate
When giving an activity which is a parent a Sequence ID, that Sequence ID is not flowed down to the children. Each child has to be manually given a Sequence ID.
I would expect that updating the parent activity's SEQ ID would at a minimum update the SEQ ID for all children which have not been manually set a SEQ ID by the user. There may still be an open question on whether we want parent IDs to override children IDs in all cases.
This is related to AERIEQS-272 Can't add SEQ ID to activity before simulation and AERIEQS-274 Sequence IDs not persistent in 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 reviewing the parent and child activity handling described in this issue, then compare the related issues AERIEQS-272 and AERIEQS-274. Determine how manually assigned child SEQ IDs should interact with inherited parent IDs, including the unresolved override question. Done means parent SEQ IDs flow to eligible children without overwriting user-set IDs, with the behavior verified in the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100