Versions Compared

Key

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

...

Section
Column


Solicitations for review

SolicitationCurrent Test Solicitation?Notes
test solicitationno; retired Sprint ??
a realistic-looking solicitationSprint 37

VLA: 4, P, L, S, C, X, Ku, K, Ka, Q

GBT: 4, P, L, S, C, X, Ku, K, Ka, Q (even if some are nonsensical for the GBT)

20DSprint 37

Specific Hardware Constraints:

GBT: P- and K-band (400 MHz, 22 GHz)

VLA: Ka- and L-band (33 GHz, 1.5 GHz)

Note: The Solicitation Json lists the basebands that are included in the solicitation.

Column
Solicitation Specific Facility/Capability for testing


a realistic-looking solicitationCapability
Facilityreal VLA ContinuumGBT Spectral Line
real VLASprint ?? >--
GBT--Sprint 28 >
VLA (replaced real VLA)Sprint 37.2




...

DescriptionJIRA/BehaviorImplementedLast WorkingTestedStatus

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

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

<Sprint 29Sprint 37Sprint 37

Status
subtletrue
colourGreen
colorgreen
titleworking

Saving within a CR

Capability Requests have their own save button. Though information looks like it is kept on the frontend, it is not in the backend without hitting save.

  • Change CR1 → don't save → navigate to CR2, change CR2 → save
    • Only changes to CR2 are kept
    • CR1 changes are not saved
  • Change CR1 → don't save → navigate to CR2, change CR2 → don't save → navigate to CR2 (changes are still present in front end) → save
    • Changes to CR1 are persisted
    • Changes to CR2 are not persisted
  • A refresh without hitting save does not persist work



  • steep learning curve. Tendency to neurotically spam the save is justified but the warning about Observation Specifications is then the punishment.
Saving and ARPersisting information between AR works the same as CR save. Navigating between ARs does not persist data unless the save button used.



Observation Specification Generation

Popup warns user is overwriting their OS.

Pops up even if no OS is currently generated or if one cannot be generated (validation needed?)

If OS cannot be generated, tab is available but empty.

Warning about "cannot generate OS" shows up.

Create Proposal

Capability (General)




Status
subtletrue
colourRed
colorgreen
titlebugs

Warning  "cannot generate OS"

  • OS exists for AR1 → add another AR→ immediately, warning appears
Navigate and Edit OS on fresh AR



Cannot Do

Create Proposal

...


Capability (General)

Can add by target3

Filtering doesn't workFiltering works

DescriptionJIRAImplementedLast WorkingTestedStatus
Scientific Justification

Jira

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.4Sprint 37.4

Status
subtletrue
colourGreen
colorgreen
titleworking

Modify text (pdf file should be no more than 4 pages) or remove entirely

Persists, can upload, can delete, can replace, can view

General Allocation Request
<Sprint 32Sprint 37.4Sprint 37.4

Modify text or remove entirely

Can Select a Facility

Can add one or more AR

Can delete AR

General Capability Requests

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

Status
subtletrue
colourGreen
colorgreen
titleworking

Can Delete

Can Add Multiples

Import Field Sources, Spectral Specs

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

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

Sprint 30Sprint 37.4Sprint 37.4

Status
subtletrue
colourGreen
colorgreen
titleworking

Zeros import.

Widget matches well to headers

There are units on the headers at import

Status
subtletrue
colourGrey
colorgreen
titleIgnored

HMS DMS doesn't import 

Units not enforced on widget

Field Source and Spectral Specs

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

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

< Sprint 30Sprint 37Sprint 37

Status
subtletrue
colourGreen
colorgreen
titleworking

 Zeros persist

Negative Numbers work as expected

Status
subtleTrue
colourYellowGrey
colorgreen
titlealmostIgnore for release

Units on fields

Precision


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

Status
subtletrue
colourGreen
colorgreen
titleworking


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 3637.4Sprint 37.34


Status
subtletrue
colourGreen
colorgreen
titleworking


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

Sprint 32Sprint 3637.4Sprint 37.34

Status
subtletrue
colourGreen
colorgreen
titleworking


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

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


Sprint 36Sprint 37.4Sprint 37.3


Status
subtletrue
colourGreen
colorgreen
titleworking

Filtering Works as expected

Import Works as expected; feedback on unsuccessful import is great!

Units exist on fields


Status
subtleTrue
colourYellow
colorgreen
titlealmost

Missing Angular Resolution for VLA

Need Units on fieldsImport Widget

  • Add FS, SS → Advanced tab → upload LAS, RMS for all sources → Performance → specify LAS, RMS, and AS
    • Advanced tab and Performance parameters don't talk to each other? Unclear hierarchy and ownership between tabs
Science Target List

Jira
showSummaryfalse
serverDMS JIRA
columnIdsissuekey,

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
colourGrey
colorgreen
titlehack for release

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 30Sprint 37.3Sprint 37.34

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

working but not scientifically checked

Status
subtletrue
colourRed
colorgreen
titlebugs

Cannot seem to affect the total time for VLA

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

< Sprint 30
Sprint 37.3
Status
subtletrue
colourGreen
colorgreen
titleworking


Status
subtleTruetrue
colourBlueGreen
colorgreen
titleFeatureworking

Can add by target

Can add by Hardware (Simple)

Moving Scans works as expectCannot yet add hardware configuration

General 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

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

Sprint 32Sprint 32Sprint 37.3

Status
subtletrue
colourGreen
colorgreen
titleworking

Times in tabs and summary are reporting consistently

Status
subtletrue
colourRed
colorgreen
titlebugs
Status
subtleTrue
colourYellowGrey
colorgreen
titlealmostIgnore for release

Precision on entries

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

Status
subtletrue
colorgreen
titleworking

...