NASA-AMMOS / NASA-AMMOS/plandev
Allow scheduling rule to assign name to activity directive
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
abercrom
https://jira.jpl.nasa.gov/browse/AERIEQS-443
Moderate
It would be useful if a scheduling rule could set the name of activity directives that it schedules. Sometimes activity types with fairly generic names are used for different purposes. This capability would allow the rule to attach a meaningful name based on the scheduling goal.
EDIT(dailis): in addition to the name, https://github.com/NASA-AMMOS/aerie/issues/777 suggests that other mission-specific metadata could be set by the scheduler.
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
No files, tests, or entry points are named. Start by locating the scheduling-rule and activity-directive implementations, then review AERIEQS-443 and issue #777 for the intended metadata scope; done should include an agreed approach for setting the directive name and coverage for the resulting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100