| Description | JIRA | Implemented | Last Working | Tested | Status | Superset of UI elements for field sources | | Jira |
|---|
| showSummary | false |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | STT-706 |
|---|
|
| Sprint 30 | Sprint 30 |
|---|
| Can Import Field Sources, Spectral Specs with CSV |
| Sprint 30 | Sprint 30 | Sprint 30 | | Status |
|---|
| subtle | true |
|---|
| color | green |
|---|
| title | working |
|---|
|
| (ahc)There is a superset of elements for Field Sources but their behavior diverges between the capabilities. Notably, the fields reset themselves in the VLA and do not in the GBT |
Modifying the TOM affects the Science Target List and the OS generation | | Jira |
|---|
| showSummary | false |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | STT-658 |
|---|
|
| Jira |
|---|
| showSummary | true |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | STT-693 |
|---|
|
| Sprint 30 |
| Sprint 30 | - (ahc) VLA: Sometimes this is true. Sometimes it is not true. The behavior is the same in real VLA and GBT Capabilities. Sources are being dropped from the TOM → STL.
- (db) GBT: working
|
| Simple partitioning, calibration strategy, and capability specific slew time and requested time calculations |
| Sprint 30 |
| Sprint 30 | - (ahc) the simple partitioning appears to be working, as well as the simple calibration strategy; The time calculation isn't displaying the information correctly in the GBT capability sometimes. I haven't tested the math behind the calculation.
- (db) GBT: RMS and requested time calculation appears to be correct in Observation Specification but not in the Science Target List
|
As a Product Owner, I would like the STL to contain The STL contains the correct Source and Hardware Configuration name to reflect what is specified by the Capability Request + TOM - The Science Targets should have a Source name, which is specified by the Field Source
- The Science Targets should have a Hardware Configuration name, which specified by the Spectral Spec
| | Jira |
|---|
| showSummary | false |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | STT-707 |
|---|
|
| Import Field Sources, Spectral Specs with CSV | Sprint 30 | Sprint 30 | Sprint 30 | | Status |
|---|
| subtle | true |
|---|
| color | green |
|---|
| title | working |
|---|
|
|
|
|
|
|
| Edit a Observation Specification to add Scans/SubScans and can filter on an Obs Spec |
| < Sprint 30 | Sprint 30One or more Capability Requests in an Allocation Request can generate one or more Observation Specifications |
|
|
Observation Specification has detailed and accurate information - e.g., Time on Observing Targets, Scan List, Overhead
| | Jira |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | STT-442 |
|---|
|
| Jira |
|---|
| server | DMS JIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | eb2e750b-a83a-387e-8345-36eee8a98f01 |
|---|
| key | STT-617 |
|---|
|
|
|
|
|
|
| One or more Capability Requests in an Allocation Request can generate one or more Observation Specifications |
|
|
|
|
|
