Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DescriptionJIRAImplementedLast WorkingTestedStatus

Create Solicitation from JSON for

  • VLA
  • GBT

not implemented/requirements not in a story:

  • modify parameters such as frequency ranges on bands

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-342

Solicitation Config Files


Sprint 16Sprint 16Sprint 30 - ahcSystem hangs for Allie



Proposal Navigation

...


DescriptionJIRAImplementedLast WorkingTestedStatus

As an Author, I would like to view my proposals.

  • in a list
  • in a detailed view (Card)

<Sprint 29<Sprint 29Sprint 29Does not seem to work correctly for Allie

Create Proposal

...


Capability (General)

DescriptionJIRAImplementedLast WorkingTestedStatus
Superset of UI elements for field sources

 

Jira
showSummaryfalse
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-706

Sprint 30
Sprint 30 - ahcahc: 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
showSummaryfalse
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-658

Sprint 30
Sprint 30 - ahcSometimes this is true. Sometimes it is not true. The behavior is the same in real VLA and GBT Capabilities
Simple partitioning, calibration strategy, and capability specific slew time and requested time calculations
Sprint 30


As a Product Owner, I would like the STL to contain 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
showSummaryfalse
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-707





VLA Capability


Expand
titleCapability Request
DescriptionJIRAImplementedLast WorkingTestedStatus






...