Versions Compared

Key

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

...

DescriptionJIRAImplementedLast WorkingTestedStatus
Scientific Justification

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-935

<Sprint 32Sprint 37.3Sprint 37.3

Status
subtletrue
colourGreen
colorgreen
titlestatus

Modify text: pdf file should be no more than 4 pages.

Can Delete Allocation Request; Capability Request; FS,

Can Rename AR,CR,FS, etc

Cannot Copy AR

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-845

< Sprint 32Sprint 32Sprint 32

Status
subtletrue
colourRed
titlestatus

Cannot delete CR 

Can Import Field Sources, Spectral Specs with CSV

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-940

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-938
Sprint 30Sprint 37Sprint 37

Status
subtletrue
colourRed
colorgreen
titlestatus

Zeros import.


HMS DMS doesn't import 

Entries in FS, SS, etc persist on save

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-939

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-937
< Sprint 30Sprint 37Sprint 37

Status
subtletrue
colourGreen
colorgreen
titlestatus

 Zeros persist

Negative Numbers work as expected



Selection of Calibration Parameters affects STL and OS
Sprint 32Sprint 32Sprint 32



Calibration Parameters

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-942

Sprint 32Sprint 36Sprint 37.3

Status
subtletrue
colourRed
colorgreen
titlestatus

Calibration parameter tab has no buttons not in VLA Continuum

Polarization Calibration Button missing in GBT Spectral Line


Performance Parameters

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-941

Sprint 32Sprint 36Sprint 37.3

Status
subtletrue
colourRed
colorgreen
titlestatus

Angular Resolution missing from Performance Parameters and Advance Tab in VLA Continuum 

Advanced Tab


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-949

Sprint 36
Sprint 37.3

Status
subtletrue
colourRed
colorgreen
titlestatus

Filtering Works as expected

Import Works as expected

Missing Angular Resolution for VLA

Need Units on fields

Science Target List

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-951

Sprint 32Sprint 37.3Sprint 37.3

Status
subtletrue
colourYellow
colorgreen
titlestatus

Removed from all tabs as it should only accessible to Product Owners and that role hasn't been configured

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

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
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




Status
subtletrue
colourYellow
titlenot implemented

Edit a Observation Specification to add Scans/SubScans and can filter on an Obs Spec

  • Add Target
  • Cannot add HardwareConfiguartion

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
serverId

< Sprint 30

eb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-945

< Sprint 30


Observation Specification


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-943

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-946

Sprint 32Sprint 32Sprint 37.3

Status
subtletrue
colourRed
colorgreen
titleworking

Times in tabs and summer are reporting consistently

Filtering doesn't work

One or more Capability Requests in an Allocation Request can generate one or more Observation Specifications
<Sprint 32Sprint 32Sprint 32

Status
subtletrue
colorgreen
titleworking

...