Versions Compared

Key

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

Updated 3.15.23 for sprint 49 (→ v0.2)

Detailed TTA Tools Sprint Feedback Page

JSON files for Solicitations, field sources, and spectral spec generation available on git repository


Table of Contents
outlinetrue

Summary of Available Solicitations, Facilities, and Capabilities



Section
Column


Solicitations for review

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

Sprint 37

Gone after Sprint 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)

20D

Sprint 37

Gone after Sprint 37

Specific Hardware Constraints:

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

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

Sem_25ASprint 38 - current, prod v0.1.2

VLA and GBT have L – Q band available

Production Solicitation for v0.1

SC_GBT_24BSprint 38 - current, prod v0.1.2

GBT only, L, S, and C band

Production Solicitation for v0.1

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

Column
Solicitation Specific Facility/Capability for testing


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

Prototype FE stories:

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

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

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

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

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




Helpful Files for Testing


FileUpdatedIntended CapabilityDescription
Sprint 38GBT Spectral Line50 Field Sources from the Megamaser use case; the use case specifics a  rms line sensitivity of 6 mJy
Sprint 38GBT Spectral Line1 Spectral Spec from Megamaser use case; Units are GHz, km/s, km/s (extra spectral spec but can delete)
Sprint 38GBT Spectral Line

General GBT Spectral Line SS.

There are 2 SS in this file: KFPA and Q band

Sprint 38VLA Continuum2 Field Sources from the polarization/continuum use case (W4); use case specifies a rms sensitivity of 100 microJy/bm. RA DEC in hms/dms.
Sprint 38VLA Continuum

2 SS (C-, X-band); Units in GHz, GHz, GHz

VLA_SS_allbands.csv

GBT_SS_allbands.csv

FieldSources_3_VLA.csv

FieldSources_3_GBT.csv

Sprint 39

v0.1.2

VLA Continuum

GBT Spectral Line

General Test Files


Easy Navigation to Jira Epics and Sprints

NameJiraDescription

Sprint 48

Jira
serverDMS JIRA
jqlQuerysprint = 154
counttrue
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01

Prototype Consensus, Finish out ISRs and hook up BE/FE ISRs + Conflicts

Feb 28

Sprint 49

Jira
serverDMS JIRA
jqlQuerySprint = 158
counttrue
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01

Due March 14: Finish hooking up ISRs (Completed/Finalized), Initiate Consensus, move Review Configuration into Solicitation tab, make views possible in UI for different roles.
Sprint 50

Jira
serverDMS JIRA
jqlQuerySprint = 160
counttrue
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01

Initiate Consensus, see (SRP) scores as Conflicted and Non Conflicted SRP member, notification on finalized ISRs and less than 3 non conflicted reviewers.
SRP Process

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

Epic
SRP Configuration

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

Epic
OSR

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

Epic
Proposal Submission

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

Epic

Feasibility Reviews

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

Epic
V0.2 Bugs

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

Epic
Solicitation Configuration

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

Epic
Proposal Bugs

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

Epic
Label: NotificationRelated

Jira
serverDMS JIRA
jqlQueryproject = "SSA TTA Tools" and labels in (NotificationRelated)
counttrue
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01

Label
Label: ConsensusReview

Jira
serverDMS JIRA
jqlQueryproject = "SSA TTA Tools" and labels in (ConsensusReview)
counttrue
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01

Label

Label: Conflicts

Jira
serverDMS JIRA
jqlQueryproject = "SSA TTA Tools" and labels in (Conflicts)
counttrue
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01

Label
Label: Configurability

Jira
serverDMS JIRA
jqlQueryproject = "SSA TTA Tools" and labels in (Configurability)
counttrue
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01

Label
Label: ISR

Jira
serverDMS JIRA
jqlQueryproject = "SSA TTA Tools" and labels in (ISR)
counttrue
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01

Label
Label: TTAMember

Jira
serverDMS JIRA
jqlQueryproject = "SSA TTA Tools" and labels in (TTAMember)
counttrue
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01

Label
Label: SRPChair

Jira
serverDMS JIRA
jqlQueryproject = "SSA TTA Tools" and labels in (SRPChair)
counttrue
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01

Label


Current Report

Landing Page


DescriptionJIRAImplementedLast WorkingTestedStatus
  • Message of the Day on landing page

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


Sprint 34Sprint 37Sprint 37

Status
subtleTrue
colorgreen
titleworking

but! it would be nice if there was more feedback when the save successful.



Notifications

DescriptionJIRAImplementedLast WorkingTestedStatus

Notification for a Submitted Proposal

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



Sprint 47Sprint 48Sprint 48

Status
subtletrue
colourGreen
colorgreen
titleworks

  • upon a successful submission, a notification is sent to a mailing list (tta-notifications-test)
  • this should be true on every resubmission
  • this should work for OSRs and PPRs

Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

  • notifications to PI/Co-Is are blocked until Identity management system is up


Notification when Review Configuration is Finalized

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

Sprint 47SprintSprint

Status
subtletrue
colourYellow
colorgreen
titleto test

  • when the Finalize button is used by a TTA member in the Review Configuration, a notification is sent to a mailing list (tta-notifications-test)
    • Allie, yes; Dana, no emailed received
  • one email is sent per panel per reviewer
    • Seems to be only per panel

Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

  • notifications per panel to SRP members/ Chairs are blocked until Identity management system is up
  • did not send an email to feasibility reveiwers (on hold)


Notification when TTA Member changes Conflict State of Reviewer

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

Sprint 47Sprint 48Sprint 48

Status
subtletrue
colourGreen
colorgreen
titleWorking

  • one email per reviewer per change is sent out to the mailing list (tta-notifications-test)

Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

  • notifications to tta member/ srp chair are blocked until Identity management system is up

Status
subtleTrue
colourYellow
colorgreen
titleReview

  • The ticket says that "Conflict Reason, and updated Conflict State" should be included in email but it is currently not
  • right now, theres is a bulk update on conflict cerification on the front end, so there are emails for every proposal instead of just the ones that were changed.


Notification when Consensus Review is finalized

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




Status
subtletrue
colourYellow
colorgreen
titleto test

  • email is sent to TTA member per panel that all consensus review have been finalized by chair


Notification when all ISRs are finalized for a panel

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





Notification when there are less than 3 available reviews for a proposal

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

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





Solicitation Creation


DescriptionJIRAImplementedLast WorkingTestedStatus

Create a Simple Solicitation from JSON for

  • VLA
  • GBT

not implemented/requirements not in a story:

  • modify parameters such as frequency ranges on bands

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

Solicitation Config Files


Sprint 16Sprint 16Sprint 30

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

Configure Field Source, SS, PP, CP





Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

Configure Advance Tab options





Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

Update/Test a solicitation when a different one is Open and has submitted proposals




Status
subtleTrue
colourBlue
colorgreen
titlenot implemented
Solicitation Tab

Sprint 37.3Sprint 37.3

Only available to TTA Member

A Proposal Prefix can be specified per solicitation

 

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

Sprint 40Sprint 40Sprint 40

Status
subtleTrue
colourBlue
colorgreen
titleWorking

Review Configuration



Status
subtleTrue
colourYellow
colorgreen
titleTesting

Review Configuration Tab is with Solicitation creation now

Create a Test Solicitation+Test Proposals
Sprint 46


Create a simple solicitation with hardcoded Science Categories and Hardware. The Proposal Process can be specified. The number of proposals it creates with 1 of 3 Science categories can be specified. The names and information on the proposal is randomly generated.

Close Solicitation

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

Sprint 45Sprint 47Sprint 47Force close a Solicitation, sending all proposals into In Review (if PPR).



Navigation



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

Status
subtleTrue
colourYellow
colorgreen
titleReview

  • would like to filter on proposals by Science Category


Saving within a CR

Capability Requests have their own save button. A user is warned if they will lose their changes from navigating.

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





Status
subtleTrue
colourGreen
colorgreen
titleworking

Saving and AR

A user is warned if they will lose their changes from navigating away.

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




Status
subtleTrue
colourGreen
colorgreen
titleworking

Observation Specification Generation

Prompt warns that 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.

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

<Sprint 35Sprint 38Sprint 38

Status
subtletrue
colourGreen
colorgreen
titleworking

Navigate and Edit OS on fresh AR



Not Implemented

Status
subtleTrue
colourGrey
colorgreen
titleignored for release

Review Tab
Sprint 43
Sprint 43

Status
subtleTrue
colourYellow
colorgreen
titleTesting

Can see panels once Review Configuration is Finalized

Can see Review Panel as SRP Member for panel which they are assigned to

Can see Review Panel as SRP Chair for panel which they are assigned to

TTA Member can see both SRP and Chair views

Submission

DescriptionJIRAImplementedLast WorkingTestedStatus
  • Submit a Proposal
  • Proposal ID and timestamp generated
  • Light Validation on Submission
  • Submission affects Proposal State
    • Submitted for PPR
    • In Review for OSR


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

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

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


Sprint 41Sprint 43Sprint 43


Status
subtleTrue
colourGreen
colorgreen
titleworking

timestamp is in MST, not local? – sprint 43 seems to be local now

Observatory Copy and Author Copy

  • As an Author:
    • Author Copy is viewable and modifiable when in Draft State and Submitted if the Solicitation is Open
    • Observatory Copy is generated when Proposal is Submitted
    • Author and Observatory Copies are both viewable if
      • the Solicitation is open
      • the Proposal State is Submitted
    • Can edit Author Copy after a submit if solicitation open
      • Can resubmit if Solicitation is open
    • Cannot edit Observatory Copy ever
    • Cannot edit an Author Copy when proposal is In Review
    • Can only see Observatory Copy after Close of Call
    • A Proposal with a Proposal State of Submitted should not be able to be deleted.
  • As TTA member:
    • Can edit Author Copy when the Proposal has any State (only up to In Review possible to test though).
      • Can Save and it persists. Should not affect Obs Copy if one exists.
      • Can Submit it (when call is open?)
    • Can edit the Observatory Copy, if one exists. Save persists and affects downstream.
    • A Proposal with a Proposal State of Hidden can be submitted if the Solictation is Open or Closed.
    • A Proposal with a Proposal State of Hidden cannot be Withdrawn
    • A Proposal with a Proposal State of Withdrawn should not appear in the Review Phase.

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

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

Sprint 42Sprint 42Sprint 42

Status
subtleTrue
colourGreen
colorgreen
titleworking

  • As an Author:
    • Author Copy is viewable and modifiable when in Draft State and Submitted if the Solicitation is Open
    • Observatory Copy is generated when Proposal is Submitted
    • Author and Observatory Copies are both viewable if
      • the Solicitation is Open
      • the Proposal State is Submitted
    • Can edit Author Copy after a submit if solicitation open
      • Can resubmit if Solicitation is open and PPR
    • Cannot edit Observatory Copy ever
    • Cannot edit or view an Author Copy when proposal is In Review
    • Can view only Observatory Copy when Proposal State is In Review
    • A Proposal with a Proposal State of Submitted should not be able to be deleted.
  • As TTA member:
    • Can edit Author Copy when the Proposal has any State (only up to In Review possible to test though).
      • Can Save and it persists. Should not affect Obs Copy if one exists.
      • Can Submit it only when call is open.

Status
subtleTrue
colourRed
colorgreen
titlebug

    • Can edit the Observatory Copy, if one exists but save applies to Author Copy only. There is no way to submit, so changes do not affect downstream (review phase) information.
    • Can withdraw a proposal in the Hidden State.
    • Withdrawn proposal still shows up in Review phase.
    • A Hidden proposal cannot be submitted, regardless of the Solicitation being open or not. It should be allowed to be submitted at anytime.

Status
subtleTrue
colourYellow
colorgreen
titlereview

  • navigating between author and observatory copy is not intuitive
  • Information in Observatory Copy is not displaying correctly or ever in OS case

Status
subtleTrue
colourRed
colorgreen
titlebug

  • Saving changes to author copy shows a warning on the list of proposals and allows resubmission  only after navigating away and then back again.  The button is not always available when it should be.
  • Submitting a proposal works but the view of the proposal is missing afterwards and until a refresh is done.


Proposal State Changes

Allowed:

  • Draft → Submitted
  • Draft → Hidden
  • Submitted → Withdrawn
  • Submitted → In Review
  • In Review → Withdrawn
  • In Review → Completed
  • Hidden → Submitted (TTA only)

Not Allowed:

  • (Submitted, In Review, Completed, Closed) → Hidden
  • Hidden → Withdrawn

Sprint 42SprintSprint 42

Status
subtleTrue
colourGreen
colorgreen
titleworking

  • submission either goes to submitted or in review (DDT); Proposal State change to Completed is out of scope for v0.2
  • Withdrawing a proposal works: the author can see the Observatory Copy but not edit either it or the author copy. Cannot even access the author copy. Tooltip shows the action is not available.

Status
subtleTrue
colourRed
colorgreen
titlebug

  • can delete a proposal which causes the state to change to hidden; however, author can see the Observatory Copy!
  • Draft → Withdrawn is currently allowed but it should not be.

Status
subtleTrue
colourYellow
colorgreen
titleReview

  • Withdraw button is only available in the edit mode of a proposal for the TTA member; it should be higher.

PPRs

PPRs - Vet Proposals


DescriptionJIRA/RequirementsImplementedLast WorkingTestedStatus
  • There is an interface with which to vet Science Categories
  • Can see the Title, Abstract, and Requested Science Category per proposal
  • the Vetted SC = the Requested SC at first, but it can be changed.
  • There is a place to record notes; they persist.
  • The proposal can be opened for viewing
  • There is a check box per proposal to indicate it has been vetted; there is a "vet all" button.
  • There is a save button


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

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

Sprint 44SprintSprint 44


Status
subtleTrue
colourYellow
colorgreen
titleReview

  • ability to filter on requested/vetted SC
  • changing a SC and back again does not revert the icon
  • front-end not hooked to back-end so viewing proposal doesn't work

Status
subtleTrue
colourRed
colorgreen
titleto fix

  • Drop down menu on available Science Categories should either be linked to Solicitations or the drop down menu on the available science categories on the vetting should be linked to the master list.


TTA Member can access vetting comments after Configuration in Finalized and forever more.




PPRs - Review Configuration


DescriptionJIRAImplementedLast WorkingTestedStatus

Panels

  • Create SRP panels with unique names
  • Delete SRP Panels
  • Associate panels with 1 or more Science Categories (edge cases)
  • Assign 1 or more SRP Chairs
  • Assign multiple SRP Members to panel
  • Auto bulk assign proposals to panels based on SC
  • Manually assign proposals to panels
  • Save
  • Feasibility groups (back burner)
  • Assign independent science review to a member of a different SRP
  • Upload and use a configuration file
  • Filtering on Panels/proposals
  • Should not be able to assign the same person to multiple panels


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

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

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

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

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

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

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

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

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

________________________

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

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

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

Sprint 43SprintSprint 43

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • can create new SRP panels
  • can select from a pre-set list of SRP panels
  • can assign SRP members/chair
  • can assign proposals to SRP

Status
subtleTrue
colourYellow
colorgreen
titleTesting

  • Automatic proposal to panel assignment based on Science Category
  • saving
  • finalizing

Status
subtleTrue
colourYellow
colorgreen
titleNot implemented

  • feasibility groups on placeholder

Status
subtleTrue
colourRed
colorgreen
titleto fix

  • Should be able to select multiple chairs (currently can only do one)
  • Want a reviewer focused display
  • Icon on number of proposals assigned to panel needs updating.
  • Drop down menu on available Science Categories should either be linked to Solicitations or the drop down menu on the available science categories on the vetting should be linked to the master list.
  • Should not be able to assign the same person to multiple panels.



Finalize Review Configuration

  • Finalize can occur when
    • all proposals are vetted
    • the Solicitation is Closed
  • Pop-up asking to confirm Finalization


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

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

Sprint 45
Sprint 47


The Finalize button is available when all proposals are vetted and SC are assigned but I can use it before the close of a Solicitation.

Status
subtleTrue
colourRed
colorgreen
titleto fix

  • Finalize button gives an error but seems to work
  • The finalize button is available before the Solicitation is Closed. It would be nice it were there but grayed out. Eventually with a tooltip that states the condition necessary for it to work.
    • If the Solicitation isn't Closed, I can see the Configured Review Panels in the Reviews tab, but the Assignment page does not populate.
  • No confirmation on Finalization
  • Error messaging should be more robust here.
  • Finalizing should prevent future edits to configuration.
Configuration and Vetting is available prior to the close of a Solicitation

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




Configuration and Vetting is part of the Solicitation UI now



PPRs - Conflict Declaration/ Role Assignments

DescriptionJIRAImplementedLast WorkingTestedStatus
  • Auto Conflicts based on authorship


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

Sprint 45Sprint 48Sprint 48


Status
subtleTrue
colourBlue
colorgreen
titleWorking


SRP Reviewer

  • Must complete Conflicts before progressing to ISRs
  • Cannot change Auto Conflict
  • Default Conflict state is Unknown
  • Reviewer must change to either Conflict or Available
  • Reviewer may enter comments; persists
  • Can view Conflict State per ISR
  • Can see Proposal ID, Abstract, and Title
  • Bulk Action of Certification (cannot certify some and not others)


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

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


Sprint 46Sprint 48Sprint 48

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • Must complete Conflicts before progressing to ISRs
  • Cannot change Auto Conflict
  • Default Conflict state is Unknown
  • Reviewer must change to either Conflict or Available
  • Reviewer may enter comments; persists
  • Can view Conflict State per ISR
  • Can see Proposal ID, Abstract, and Title
  • Bulk Action of Certification (cannot certify some and not others)

Status
subtleTrue
colourYellow
colorgreen
titlenot implemented

Status
subtleTrue
colourRed
colorgreen
titleto fix


SRP Chair

  • must complete conflicts like a reviewer
  • can see a "matrix" of Reviewers in their panel and their Conflict State
  • can assign Review Type per ISR
    • Only 1 Primary, 1 Secondary, * Tertiary, * None per Proposal
    • Default is None
    • Can change Review Types unless ISR is Finalized
  • Should not be able to assign types of Conflicted reviewers

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

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

Sprint 46/47

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • must complete conflicts like a reviewer
  • can see a "matrix" of Reviewers in their panel and their Conflict State
  • Only one Primary and one Secondary can be saved to a proposal.
  • Any number of None or Teritary can be saved to a proposal.

Status
subtleTrue
colourYellow
colorgreen
titlenot implemented


Status
subtleTrue
colourRed
colorgreen
titleto fix

  • should not be able to assign Review Types to a conflicted reviewer

TTA Member

  • Can change Conflict State of reviewers
  • Valid Conflict State transitions for a TTA Member:
    • Available → Available
    • Available → Conflict
    • Conflict → Available
    • Conflict → Conflict
    • AutoConflict → Available
  • Proposed Consequences:
    • ISRs either become available or unavailable as necessary for the SRP Member.
    • ISRs that are now Conflict State of Conflict that had Review Types other than None should automatically have Review Types changed to None.
  • Notifications sent

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

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

Sprint 45/47

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • Can update Conflict state and Certify (preferrable that it is done after user certifies)

Status
subtleTrue
colourRed
colorgreen
titleto fix

  • ISRs are not affected downstream yet.

PPRs - ISRs

DescriptionJIRAImplementedLast WorkingTestedStatus
  • SRP Reviewer
    • See list of proposals (after conflict certification)
    • Review Type is displayed
      • Default is None; otherwise P,S,T
    • Review State is displayed
      • default is Blank; otherwise Saved, Completed, Finalized, Closed
    • Conflict State is displayed
      • Conflict/Available
    • If not Conflicted, have an ISR in which to enter comments and a score and see the proposal
      • can Save (Review State → Saved) per ISR
        • validate if score not equal to 0; otherwise it cannot save
        • does not validate comments
      • can Complete (Review State → Completed) per ISR
      • can Finalize (bulk action) if any ISRs with Review not equal to None are not Closed or Finalized
    • If Conflicted, only see title, abstract, proposal ID and cannot enter any information
  • All comments and scores are saved (though not propagated to consensus; see later)
  • Normalized Individual Scores are calculated on Finalize
  • Edge cases to test:
    • If an external proposal is added after reviewer has finalized, they should be able to review and finalize that one proposal (finalize is still bulk in theory)
    • If consensus has started for their panel, the Finalized Normalized Individual Score in that panel may be inconsistent with their new Normalized Individual Score (since it has the extra proposal). This is acceptable.


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

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

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

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


Sprint 46, 47SprintSprint

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • SRP Reviewer
    • See list of proposals (after conflict certification)
    • Review Type is displayed
      • Default is None; otherwise P,S,T
    • Review State is displayed
      • default is Blank; otherwise Saved, Completed, Finalized, Closed
    • If not Conflicted, have an ISR in which to enter comments and a score and see the proposal
      • can Save (Review State → Saved) per ISR
        • validate if score not equal to 0; otherwise it cannot save
        • does not validate comments
    • All comments and scores are saved (though not propagated to consensus; see later)

Status
subtleTrue
colourYellow
colorgreen
titleTesting

  • can Complete (Review State → Completed) per ISR
  • can Finalize (bulk action) if any ISRs with Review not equal to None are not Closed or Finalized

Status
subtleTrue
colourYellow
colorgreen
titlenot implemented

  • If Conflicted, only see title, abstract, proposal ID and cannot enter any information
  • Conflict State is displayed
    • Conflict/Available

Status
subtleTrue
colourRed
colorgreen
titleto fix

  • Conflict state not preventing visibility to proposals when appropriate

TTA Member

  • can change Review State to Closed
    • Auto changes Review Type to None
  • If a TTA member Finalizes a SRP member's ISRs (for the reviewer), it will finalize the ISRs that have a valid comment and score (Review State of Saved, Completed) and Review Type not equal to None. If a comment+score is not valid, regardless of the Review Type, it will Close the ISR (unsure if it still ignores review types of None)

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




Status
subtleTrue
colourBlue
colorgreen
titleto test

  • When TTA member uses Finalize, as a bulk action for all ISRs for that reviewer
    • Review Types of Primary, Secondary, Tertiary but have Review State of Blank are set to Close
    • Review Type of None is ignored, regardless of Review State
    • Review Types of P,S,T that have Review States in (Saved, Completed) are transitioned to Finalized
  • A separate Close functionality will be per ISR

PPRs - Consensus

DescriptionJIRAImplementedLast WorkingTestedStatus

SRP Member

  • As a conflicted SRP member, only see the SRP scope, proposal ID, title, abstract
  • As a non-conflicted SRP member, I want to see the comments, scores, and proposals for which I am not conflicted
    • Comments are not connected to reviewers
    • Normalized Individual Score
    • Finalized Normalized Individual Score
    • Mean Normalized Score
    • Standard Deviation of the Mean Normalized Score
    • SRP Score
  • As a non-conflicted SRP member and with a Review Type of Primary or Secondary, I want to enter consensus comments.
  • All members that are not conflicted can view Consensus comments
  • Be able to see the updated SRP score, if it is changed by the chair or via changes to the Finalized Normalized Individual Score. Push or refresh.
  • See Feasibility Reviews (on hold)
  • As a Primary or Secondary, I want to complete a consensus comment
    • Members can no longer edit, but chair can
  • Import/Export Consensus Comments


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

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

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

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

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

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

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

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

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

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

SprintSprintSprint

Status
subtleTrue
colourBlue
colorgreen
titleto test

  • Review States of Closed should have Review Types of None should not affect the Consensus Reviews
  • Review States of Any and Review Type of None should not affect the Consensus Reviews
  • Primary and Secondary should be able to enter scores and comments and complete consensus reviews.

Status
subtleTrue
colourBlue
colorgreen
titleWorking

Status
subtleTrue
colourYellow
colorgreen
titlenot implemented

Status
subtleTrue
colourRed
colorgreen
titleto fix


SRP Chair

  • Overview of consensus comment state (Completed, Saved)
  • Overview of Review Types and Conflict State
  • Ability to change SRP Score directly
  • Update Finalized Normalized Individual Scores
    • Forces update to MNS, STD_MNS, and SRP if the SRP score was not manually changed already
  • Have visibility to past disposition letters
  • Review Consensus comments, modify comments, and finalize Consensus Reviews
  • History of Changes of Consensus Reviews to be kept

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

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

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

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

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





Status
subtleTrue
colourBlue
colorgreen
titleWorking

Status
subtleTrue
colourYellow
colorgreen
titlenot implemented

Status
subtleTrue
colourRed
colorgreen
titleto fix


TTA Member

  • Initiate Consensus per panel if all ISRs are Finalized
  • Generate Normalized Linear Rank when all consensus reviews are finalized per panel.

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

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




Status
subtleTrue
colourBlue
colorgreen
titleWorking

Status
subtleTrue
colourYellow
colorgreen
titlenot implemented

Status
subtleTrue
colourRed
colorgreen
titleto fix


OSR Reviews

DescriptionJIRAImplementedLast WorkingTestedStatus
  • Enter Comments for
    • Science
    • Technical
    • Data Management
  • Enter Binary Score
  • View Proposal
  • Save
  • Finalized (no complete here)


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

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

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

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

Sprint 43Sprint 43Sprint 43

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • Can enter comments for PI, Technical, Data Management + an internal for each
  • Score
    • Needs to be Binary
  • Can Save
  • Can Finalize which "dangles" but next step is out of scope. It does change the review state to Finalized, as expected. Proposal State doesn't change yet (not in scope).

Status
subtleTrue
colourYellow
colorgreen
titlenot implemented

  • Hard to tell which proposals have been reviewed.

Status
subtleTrue
colourRed
colorgreen
titleto fix

Score needs to be binary

Version 0.3 Outline

DescriptionJIRAImplementedLast WorkingTestedStatus

Scheduler (during ISRs)

  • Source Conflicts






Scheduler (post Consensus)

  • Construct Preliminary Allocation Dispositions (priorities and time)
    • Inputs:
      • Proposal Information (current Semester):
        • Sources, Resources
          • Cluster ID; Time; LST/GST range, Config (VLA); Band;Fixed Date?
        • Linear Ranks
      • Other:
        • Carryover from previous semesters
        • Sponsored time
        • Maintenance Time
    • Fine Tuning inputs
      • Manual inspection of carryover etc
    • Algorithm to determine scheduling priorities and available time
      • How initial priorities are determined are Facility specific
        • e.g., VLBA is straight quartiles
    • Fine Tuning
      • Manual inspection of pressure plot
      • Annotate recommendations
        • e.g., promote N → C to fill gaps
    • Output to TAC
      • Cluster ID; Time; LST/GST range, Config (VLA); Band; Priority
      • Pressure Plots





Mechanism to track project completion (Need for carryover)




Create Proposal



Capability (General)

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 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

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

General Allocation Request
<Sprint 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Can Select a Facility

Can add one or more AR

Can delete AR

Can rename

General Capability Requests

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

< Sprint 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

Can Delete

Can Add Multiples

Can Rename

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

Sprint 30

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

Zeros import.

Widget matches columns to headers mostly as excepted (doesn't match units)

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

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

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


< Sprint 30

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 38

Status
subtleTrue
colourBlue
colorgreen
titleprod


Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

 Zeros persist in fields

Entries persists

Status
subtletrue
colourRed
colorgreen
titlebug

Negative Values in Dec DMS entry do not display correctly

Status
subtleTrue
colourGrey
colorgreen
titleIgnore for release

Units on fields

Precision

Status
subtleTrue
colourGrey
colorgreen
titleconfiguration feature

GBT missing field of view shape text entries and labels for non point source requests


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 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

  • VLA
    • Polarization calibration triggers
      • Pol Angle scan
      • Leakage scan
  • GBT
    • Polarization calibration triggers
      • leakage scan
    • Test Source triggers test source scan
    • flux density triggers flux density scan
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 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

  • VLA
    • Angular Resolution - degree +
    • LAS - degree +
    • RMS - Jy/beam
  • GBT
    • Angular Resolution - degree +
    • RMS - Jy/beam

Advanced Tab


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

Jira
showSummarytrue
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-975

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

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

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

Sprint 36

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

Filtering Works as expected

Units exist on fields

Angular Resolution is present for VLA

Import Widget has units

Status
subtleTrue
colourRed
colorgreen
titlebug

Import Works as expected; feedback on unsuccessful import (was) great! Now it thinks nothing works when only 1 thing is bad. STT-993


Status
subtleTrue
colourYellow
colorgreen
titleReview

Relationship and hierarchy on Advanced Tab + Performance Parameters

  • Add FS, SS → Advanced tab → upload LAS, RMS for all sources → Performance → specify LAS, RMS, and AS
    • behavior is understood in ticket 992. Need more feedback but behavior acceptable.
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

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

Sprint 30

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

working but not scientifically checked

Editing Observation Specification

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

< Sprint 30Sprint 37.4Sprint 37.4

Status
subtletrue
colourGreen
colorgreen
titleworking

Can add by target

Can add by Hardware (Simple)

Moving Scans works as expect

General Observation Specification


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

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

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

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

Sprint 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

Times in tabs and summary are reporting consistently

Filtering works

Status
subtleTrue
colourGrey
colorgreen
titleIgnore for release

Precision on entries

Status
subtleTrue
colourRed
colorgreen
titlebug

GBT time calculation uses bandwidth instead of spectral resolution.

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

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colorgreen
titleworking




Version Reports

Expand
titleversion 0.1 report

Landing Page

Updated 10.12.22 for sprint 39, v0.1.2




DescriptionJIRAImplementedLast WorkingTestedStatus
  • Message of the Day on landing page

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


Sprint 34Sprint 37Sprint 37

Status
subtleTrue
colorgreen
titleworking

but! it would be nice if there was more feedback when the save successful.


Solicitation Creation




DescriptionJIRAImplementedLast WorkingTestedStatus

Create a Simple Solicitation from JSON for

  • VLA
  • GBT

not implemented/requirements not in a story:

  • modify parameters such as frequency ranges on bands

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

Solicitation Config Files


Sprint 16Sprint 16Sprint 30

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

Configure Field Source, SS, PP, CP





Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

Configure Advance Tab options





Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

Update/Test a solicitation when a different one is Open and has submitted proposals




Status
subtleTrue
colourBlue
colorgreen
titlenot implemented
Solicitation Tab

Sprint 37.3Sprint 37.3

Only available to TTA Member



Navigation



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

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




  • steep learning curve. Tendency to neurotically spam the save is justified but the warning about Observation Specifications is then the punishment.

Status
subtleTrue
colourYellow
colorgreen
titleReview

Saving and AR

Persisting information between AR works the same as CR save. Navigating between ARs does not persist data unless the save button used.

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




Status
subtleTrue
colourYellow
colorgreen
titleReview

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.

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

<Sprint 35Sprint 37.5Sprint 37.5

Status
subtletrue
colourGreen
colorgreen
titleworking

Navigate and Edit OS on fresh AR



Not Implemented

Status
subtleTrue
colourGrey
colorgreen
titleignored for release

Create Proposal



Capability (General)

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

< Sprint 32Sprint 37.4Sprint 37.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
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-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
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-948

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

< Sprint 30Sprint 37Sprint 37

Status
subtletrue
colourGreen
colorgreen
titleworking

 Zeros persist

Negative Numbers work as expected

Status
subtleTrue
colourGrey
colorgreen
titleIgnore 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 37.4Sprint 37.4

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

Status
subtletrue
colourGreen
colorgreen
titleworking

Advanced Tab


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

Jira
showSummarytrue
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-975

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

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

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

Sprint 36Sprint 37.4Sprint 37.5

Status
subtletrue
colourGreen
colorgreen
titleworking

Filtering Works as expected

Units exist on fields

Angular Resolution is present for VLA

Import Widget has units

Status
subtleTrue
colourRed
colorgreen
titlebug

Import Works as expected; feedback on unsuccessful import (was) great! Now it thinks nothing works when only 1 thing is bad. STT-993


Status
subtleTrue
colourYellow
colorgreen
titleReview

Relationship and hierarchy on Advanced Tab + Performance Parameters

  • Add FS, SS → Advanced tab → upload LAS, RMS for all sources → Performance → specify LAS, RMS, and AS
    • behavior is understood in ticket 992. Need more feedback but behavior acceptable.
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

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

Sprint 30Sprint 37.3Sprint 37.4

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

working but not scientifically checked

Editing Observation Specification

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

< Sprint 30Sprint 37.4Sprint 37.4

Status
subtletrue
colourGreen
colorgreen
titleworking

Can add by target

Can add by Hardware (Simple)

Moving Scans works as expect

General Observation Specification


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

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

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

Sprint 32Sprint 37.5Sprint 37.5

Status
subtletrue
colourGreen
colorgreen
titleworking

Times in tabs and summary are reporting consistently

Filtering works

Status
subtleTrue
colourGrey
colorgreen
titleIgnore for release

Precision on entries

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

Status
subtletrue
colorgreen
titleworking





Misc


Expand
titleHidden For later

Display Precision

  • Coordinate Units:
    • GMVA can have 1e-5 arcsecond precision astrometry. For degrees, this looks like 1e-9 deg
    • R.A. (J2000): 24.422080962 deg   Dec. (J2000): +33.159759164 deg  with precision to the 9th decimal place.
    • R.A. (J2000): 01:37:41.29966 Dec. (J2000): +33:09:35.08039 with a precision to the 5th decimal place.
  • Parallax  has a precision of 1e-5 milli arcsecond
  • Proper motions have a precision of 1e-5 milli arcsecond/yr
  • Radial Velocity has a precision of 1e-3 km/s
  • Flux Density units (peak or rms) have a precision of 1e-7
  • Line widths have a precision of 1e-5 km/s
  • Frequency (bandwidth, spectral resolution) has a precision of 1e-5 GHz or 1e-5 km/s
  • Angles (angular resolution, largest angular scale) 1e-5 arcsec