NASA-AMMOS / NASA-AMMOS/plandev
Track expansion run status in the database
Open
Nobody has claimed this yet.
feature
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
We need to reflect the status of an expansion run in the database. This should be similar to how we store simulation and scheduling statuses.
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 how simulation and scheduling statuses are stored in the database, then trace the expansion-run persistence path. Confirm the expected expansion status values and update points with the project context; done means expansion-run status is reflected consistently alongside those existing statuses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100