Updated 102.5.23 for sprint 47 (→ v0.2)01.2024

Table of Contents

outline	true

Summary of Available Solicitations, Facilities, and Capabilities

...

...

Section
Column

Solicitations for review
Solicitation Current Test Solicitation? Notes
test solicitation no; 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_25A Sprint 38 - current, prod v0.1.2
VLA and GBT have L – Q band available
Production Solicitation for v0.1
SC_GBT_24B Sprint 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 solicitation Capability
Facility VLA Continuum GBT Spectral Line
real VLA Sprint ?? > --
GBT -- Sprint 28 >
VLA (replaced real VLA) Sprint 37.2
Prototype FE stories:
Jira
server DMS JIRA
columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId eb2e750b-a83a-387e-8345-36eee8a98f01
key STT-1142
Jira
server DMS JIRA
columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId eb2e750b-a83a-387e-8345-36eee8a98f01
key STT-1007
Jira
server DMS JIRA
columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId eb2e750b-a83a-387e-8345-36eee8a98f01
key STT-1060
Jira
server DMS JIRA
columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId eb2e750b-a83a-387e-8345-36eee8a98f01
key STT-1167
Jira
server DMS JIRA
columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId eb2e750b-a83a-387e-8345-36eee8a98f01
key STT-1088

Helpful Files for Testing

File	Updated	Intended Capability	Description
GBTmegamaser_FS_50.csv	Sprint 38	GBT Spectral Line	50 Field Sources from the Megamaser use case; the use case specifics a rms line sensitivity of 6 mJy
GBTmegamaser_SS_1.csv	Sprint 38	GBT Spectral Line	1 Spectral Spec from Megamaser use case; Units are GHz, km/s, km/s (extra spectral spec but can delete)
GBTSpectralLine_SS_2.csv	Sprint 38	GBT Spectral Line	General GBT Spectral Line SS. There are 2 SS in this file: KFPA and Q band
VLAContinuum_FS_2.csv	Sprint 38	VLA Continuum	2 Field Sources from the polarization/continuum use case (W4); use case specifies a rms sensitivity of 100 microJy/bm. RA DEC in hms/dms.
VLAContinuum_SS_2.csv	Sprint 38	VLA 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

Current Report

...

Easy Navigation to Jira Epics and Sprints

Name	Jira	Description

JIRAImplementedLast WorkingTestedStatus

Message of the Day on landing page

JirashowSummaryfalse

Sprint 48

Jira

server	DMS JIRA

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionDescriptionJIRAImplementedLast WorkingTestedStatus

Notification for a Submitted Proposal

jqlQuery	sprint = 154
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

keySTT-754Sprint 34Sprint 37Sprint 37

Status

subtle	True
color	green
title	working

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

Notifications

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

Feb 28

Sprint 49

Jira

server	DMS JIRA
jqlQuery	Sprint = 158
count	true
serverId	eb2e750b-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

server	DMS JIRA

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

jqlQuery	Sprint = 160
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

keySTT-924Sprint 47SprintSprint 47 StatussubtletruecolourGreencolorgreentitleworks

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

StatussubtleTruecolourBluecolorgreentitlenot implemented

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

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

Sprint 51

Jira

server	DMS JIRA
jqlQuery	sprint = 161
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

Consensus Comments and consensus related Scores, ability to export a file for ISR comments and score

Start of UI overhaul

Sprint 52

Jira

server	DMS JIRA
jqlQuery	sprint = 162
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

Start UI/DM/CA reconciliation

Utility functions: upload/export ISRs, print proposals

BE work on finalizing consensus and generating NRL

Sprint 53

Notification when Review Configuration is Finalized

Jira

server	DMS JIRA

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

jqlQuery	sprint = 175
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

keySTT-882Sprint 47SprintSprint StatussubtletruecolourYellowcolorgreentitleto 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

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

Refactoring 1/?

Sprint 54

Jira

server	DMS JIRA
jqlQuery	sprint = 176
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

Refactoring 2/?

Sprint 55

Jira

server	DMS JIRA
jqlQuery	sprint = 180
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

Refactoring 3/?

Sprint 56

Jira

server	DMS JIRA
jqlQuery	sprint = 183
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

Refactoring 4/?

Sprint 57

Sprint 58

Notification when TTA Member changes Conflict State of Reviewer

Jira

jqlQuery
server	DMS JIRA

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

sprint = 191
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

keySTT-1145Sprint 47Sprint 47Sprint 47 StatussubtletruecolourYellowcolorgreentitleto test

one email per reviewer per change is sent out to the mailing list (tta-notifications-test)
right now, theres is a bulk update on conflict cerification on the front end, so there are a lot of emails

StatussubtleTruecolourBluecolorgreentitlenot implemented

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

StatussubtleTruecolourYellowcolorgreentitleReview

The ticket says that "Conflict Reason, and updated Conflict State" should be included in email but it is currently not

Notification when Consensus Review is finalized JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

connecting FE/BE consensus. System fully connected

Sprint 59

Jira

server	DMS JIRA
jqlQuery	sprint = 199
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

bug hunting and final feature push

Sprint 60

Jira

server	DMS JIRA
jqlQuery	issueKey in (STT-1202,STT-1323,STT-1324,STT-1325,STT-1330,STT-1336,STT-1338,STT-1341,STT-1351,STT-1357,STT-1358,STT-1360,STT-1369,STT-1376,STT-1378,STT-1379,STT-1381,STT-1382,STT-1384,STT-1387,STT-1388,STT-1394,STT-1395,STT-1398,STT-1404,STT-1406,STT-1205,STT-1349,STT-1355,STT-1393,STT-1397,STT-1401,STT-1403,STT-1407,STT-1156,STT-1399)
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

keySTT-914

bug hunting and final feature push

Sprint 61

Jira

count
server	DMS JIRA
jqlQuery	sprint = 214

Statussubtle

	true

colourYellowcolorgreentitleto 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

serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

bug hunting; final official sprint of version 0.2

Sprint 62

Jira

server	DMS JIRA
jqlQuery	sprint = 217
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

prototype v0.2.1 interface; RIDs for internal view

SRP Process

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

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

930

Epic

SRP Configuration

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

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

JirashowSummaryfalse

929

Solicitation Creation

Epic

OSR

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

342

438

Solicitation Config Files

Sprint 16Sprint 16Sprint 30 StatussubtleTruecolourGreycolorgreentitlehack for releaseConfigure Field Source, SS, PP, CP StatussubtleTruecolourBluecolorgreentitlenot implementedConfigure Advance Tab options StatussubtleTruecolourBluecolorgreentitlenot implementedUpdate/Test a solicitation when a different one is Open and has submitted proposals StatussubtleTruecolourBluecolorgreentitlenot implementedSolicitation TabSprint 37.3Sprint 37.3

Only available to TTA Member

A Proposal Prefix can be specified per solicitation Jiraserver

Epic

Proposal Submission

Jira

server

DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

866

434

Sprint 40Sprint 40Sprint 40 StatussubtleTruecolourBluecolorgreentitleWorkingReview TabSprint 43Sprint 43 StatussubtleTruecolourBluecolorgreentitleWorking

Reviews configuration tab is available for TTA member

StatussubtleTruecolourRedcolorgreentitlebug

Review Configuration tab is accessible for non tta member. Non-TTA member can't do anything or really see anything though.

Create a Test Solicitation+Test ProposalsSprint 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.

Epic

Feasibility Reviews

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1035

Epic

V0.2 Bugs

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1059

Epic

Solicitation Configuration

Close Solicitation

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

1141DescriptionJIRA/BehaviorImplementedLast WorkingTestedStatus

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

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

<Sprint 29Sprint 37Sprint 37 StatussubtletruecolourGreencolorgreentitleworking StatussubtleTruecolourYellowcolorgreentitleReview

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.

JirashowSummaryfalseserverDMS JIRA

932

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

Epic

Proposal Bugs

Jira

server	DMS JIRA

columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

976

1034

status

Epic

subtle

Label: NotificationRelated

True

Jira

colour

server

GreencolorgreentitleworkingSaving and ARA user is warned if they will lose their changes from navigating away.

DMS JIRA
jqlQuery	project = "SSA TTA Tools" and labels in (NotificationRelated)
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

Label

Label: ConsensusReview

Jira

server	DMS JIRA

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

jqlQuery	project = "SSA TTA Tools" and labels in (ConsensusReview)
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

keySTT-976 StatussubtleTruecolourGreencolorgreentitleworkingObservation 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.

Label

Label: Conflicts

Jira

server	DMS JIRA
jqlQuery	project = "SSA TTA Tools" and labels in (Conflicts)
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

Label

Label: Configurability

Jira

server	DMS JIRA

columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

jqlQuery	project = "SSA TTA Tools" and labels in (Configurability)
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

keySTT-972<Sprint 35Sprint 38Sprint 38 StatussubtletruecolourGreencolorgreentitleworkingNavigate and Edit OS on fresh AR

Not Implemented

StatussubtleTruecolourGreycolorgreentitleignored for release

...

Label

Label: ISR

Jira

server	DMS JIRA
jqlQuery	project = "SSA TTA Tools" and labels in (ISR)
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

Label

Label: TTAMember

Jira

server	DMS JIRA
jqlQuery	project = "SSA TTA Tools" and labels in (TTAMember)
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

Label

Label: SRPChair

Jira

server	DMS JIRA
jqlQuery	project = "SSA TTA Tools" and labels in (SRPChair)
count	true
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

Label

Current Report

Landing Page

...

Description	JIRA	Implemented	Last Working	Tested	Status

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

Message of the Day on landing page

Jira

showSummary

JirashowSummary

	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

850 JirashowSummaryfalse

754

Sprint 34

Sprint 37

Status

subtle	True
color	green
title	working

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

Notifications

Description

JIRA

Implemented

Last Working

Tested

Status

Notification for a Submitted Proposal

emails are sent to the specified emails informing the TTA member, PIs/coPIs of a successfull submission

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

860

924

jira

Sprint 47

showSummaryfalseserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumns

Sprint 68

V0.2

Sprint 68

V0.2

Status


subtle	true
colour	Green
color	green
title	works

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


subtle	True
colour	Blue
color	green
title	not implemented

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

Notification when Review Configuration is Finalized

emails are sent to SRP members and chairs when the panels have been configured.

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

851

882

Sprint

41

47

Sprint

43

68

Sprint 43

V0.2

Sprint 68

V0.2

Status

subtle

True

title
true
colour	Green
color	green

working

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

Observatory Copy and Author Copy

Sprint 42Sprint 42Sprint 42

Working

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)

Status

colour

subtle	True

Green

title
Blue
color	green

working

Author and Observatory Copies are available (when appropriate)
Can edit Author Copy after a submit if solicitation open
Cannot edit Observatory copy unless TTA member
Cannot edit an author copy when proposal is In Review

not implemented

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

Notification when TTA Member changes Conflict State of Reviewer

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1145

Sprint 47

Sprint 68

V0.2

Sprint 68

V0.2

Status


subtle	true
colour	Green

StatussubtleTruecolourYellow

title

color	green

reviewnavigating between author and observatory copy is not intuitive

Working

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

Status

colour

subtle	True

Red

title
Blue
color	green

bug

not implemented

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.
Information in Observatory Copy is not displaying correctly or ever in OS case

Proposal State Changes

Sprint 42SprintSprint 42

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

Status

colour

subtle	True

Green

title
Yellow
color	green

working

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.

Review

The ticket says that "Conflict Reason, and updated Conflict State" should be included in email but it is currently not
right now, there is a bulk update on conflict certification 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

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-914

Status


subtle	true
colour	Green

StatussubtleTruecolourRedcolorgreentitlebug

can delete a proposal which causes the state to change to hidden; however, author can see the Observatory Copy!

StatussubtleTruecolourYellow

title

color	green

Review

Working

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

PPRs

PPRs - Vet Proposals

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

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

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

874server

1036

Jira

Sprint 50

Sprint 68

V0.2

Sprint 68

V0.2

Status


subtle	true
colour	Green
color	green
title	Working

Notification when there are less than N available reviews for a proposal.

When a reviewer certifies conflicts, all of the proposals that do not have at least N available or unknown reviewers per proposal are sent in a single email.
The list in the email will have all of the proposals affected. It is triggered when SRP members certify. It does not trigger when the auto conflicts are managed.
N is a configurable number

Jira

server

DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

890

1037

Sprint 44

Jira

Sprint

server

Sprint 44

DMS JIRA

StatussubtleTruecolourYellowcolorgreentitleReview

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

columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1182

Sprint 50

Sprint 61

V0.2

Sprint 61

V0.2

Status

subtle

True

colour
true

Red

title
Green
color	green

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

...

Working

tta member can specifiy per panel the minimum number of reviewers. the default is three
email is sent to TTA list if a proposals has M number of available or unknown reviewers if M < N

Solicitation Creation

...

Description	JIRA	Implemented	Last Working	Tested	Status

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

Jira

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

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

867serverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverIdeb2e750b-a83a-387e-8345-36eee8a98f01keySTT-870

342

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-868

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-869

Jira

Solicitation Config Files

Sprint 16

Sprint 30

Status


subtle	True
colour	Grey
color	green
title	hack for release

Configure Field Source, SS, PP, CP

Status


subtle	True
colour	Blue
color	green
title	not implemented

Configure Advance Tab options

Status


subtle	True
colour	Blue
color	green
title	not implemented

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

Status


subtle	True
colour	Blue
color	green
title	not implemented

Solicitation Tab

Sprint 61

V0.2

Sprint 61

V0.2

Only available to TTA Member

A Proposal Prefix can be specified per solicitation

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

872

866

JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution

Sprint 40

Status


subtle	True
colour	Blue
color	green
title	Working

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

columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverIdeb2e750b-a83a-387e-8345-36eee8a98f01keySTT-883

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

1066

1141

jira

Sprint 45

Sprint 61

V0.2

Sprint 61

V0.2

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

...

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-998

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1077

________________________

Jira

Description

JIRA/Behavior

Implemented

Last Working

Tested

Status

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

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

<Sprint 29

Sprint 37

Status


subtle	true
colour	Green
color	green
title	working

Status


subtle	True
colour	Yellow
color	green
title	Review

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

showSummary	false

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

896

976

Status


subtle	True
colour	Green
color	green
title	working

Saving and AR

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

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,

JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,

duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

897

976

Status


subtle	True
colour	Green
color	green
title	working

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

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

898

972

Sprint 43

<Sprint 35

Sprint 38

Sprint

43

38

Status

subtle

True

colour
true

Blue

title
Green
color	green

Working

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

working

Navigate and Edit OS on fresh AR

Not Implemented

Status

colour
subtle	True

Yellow

title
Grey
color	green

not implemented

not automatic yet based on Science Category

saving

finalizing

feasibility groups on placeholder

	ignored for release

Review Tab

Sprint 43

Sprint 61

V0.2

Sprint 61

V0.2

Status

colour

subtle	True

Red

title
Blue
color	green

to fix

Working

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

Description

JIRA

Implemented

Last Working

Tested

Status

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

Jira

showSummary	false

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.
Automate the assigning of proposals to panels.

Finalize Review Configuration

Finalize can occur when
- all proposals are vetted
- the Solicitation is Closed

jira


server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

884

850

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

889

860

Sprint 45

Jira

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.

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

Configuration and Vetting is available prior to the close of a Solicitation JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

1168Currently if you open a Solicitation and then go to reviews (without closing the Solicitation), you cannot see the Solicitation at all. If you hit refresh, then you can configure the review.

PPRs - Conflict Declaration/ Role Assignments

851

Sprint 41

Sprint 43

Status


subtle	True
colour	Green
color	green
title	working

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.

DescriptionJIRAImplementedLast WorkingTestedStatus

Auto Conflicts based on authorship

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-884

Sprint 45SprintSprint

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

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

885

863

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

875

861

Sprint

46

42

Sprint 42

Status

colour

subtle	True

Blue

title
Green
color	green

Working StatussubtleTruecolourYellowcolorgreentitlenot implemented

working

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

title

subtle	True
colour	Red
color	green

to 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

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-887

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-871

Sprint 46/47

bug

- 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


subtle	True
colour	Yellow
color	green
title	review

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

Status


subtle	True
colour	Red
color	green
title	bug

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 42

Sprint

Sprint 42

StatussubtleTruecolourBluecolorgreentitleWorking

Status

colour

subtle	True

Yellow

title
Green
color	green

not implemented

Any number of primary, secondary can be assigned currently
Certified indicator is not hooked up on FE
Save is not available on FE
Summary information on FE does not update yet

working

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


subtle	True
colour	Red
color	green
title	bug

to fix

TTA Member

Can change Conflict State of reviewers
Notifications sent

JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,

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


subtle	True
colour	Yellow
color	green
title	Review

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

Print a single or multiple proposals

A user can print a proposal or more
the science justification is included in the view
all of the components of the proposal are concluded in the view (need definition)

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

886

915

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

1146

916

Sprint

45/47

52

Status

colour

subtle	True

Red

title
Green
color	green

to fix

Bulk update only on all conflicts in FE currently; BE could support it
No visual indication that update has occurred; refresh necessary

PPRs - ISRs

	working

Back end supports printable view

Status


subtle	True
colour	Yellow
color	green
title	Review

Navigation to this functionality missing in UI

Status


subtle	True
colour	Red
color	green
title	bug

Print view is missing Observation Specifications (need to tackle larger DM issues maybe)

Print view is missing Science Justification (might be a trade off with other issues)

PPRs

PPRs - Vet Proposals

...

Description	JIRA/Requirements

DescriptionJIRA

	Implemented	Last Working	Tested	Status

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:

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.
the vetting/panel assignment configuration persists
proposals can be assigned to a panel
Hidden proposals are not shown in Vetting; i.e., only those with Proposal States of In Review
Changing a SC and back again reverts the badge appropriately
Guidance Text to tell TTA member missing components necessary to Finalize (vet all, assign panels, create panels per SC, chair assigned to panel)

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-874

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 Noramlized Individual Score (since it has the extra proposal). This is acceptable.

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

877

890

jira

Sprint 44

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-878

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

changing a SC and back again reverts the icon
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.
Changes persist
proposals can be assigned to panels
Hidden proposals are not shown in Vetting; i.e., only those with Proposal States of In Review

Status


subtle	True
colour	Red

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-873

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-879

Sprint 46, 47SprintSprint StatussubtleTruecolourBlue

title

color	green

Working StatussubtleTruecolourYellowcolorgreentitlenot implemented

Reviewers cannot see Reviews yet; only TTA members have views into ISRs
Not Finalize or Complete buttons yet

StatussubtleTruecolourRedcolorgreentitleto fix

TTA Member

can change Review State to Closed
- Auto changes Review Type to None

JiraserverDMS JIRAcolumnIds

to 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

...

Description

JIRA

Implemented

Last Working

Tested

Status

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 unique SRP Members to panel
SRP members can only belong to one panel
Auto bulk assign proposals to panels based on SC (in vetting UI)
Manually assign proposals to panels (in vetting UI)
Changes to panel persist
Feasibility groups (back burner)
Upload and use a configuration file
Filtering on Panels/proposals
Can delete reviewers
Guidance Text to tell TTA member missing components necessary to Finalize (vet all, assign panels, create panels per SC, chair assigned to panel)

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

1039

867

...

Jira

Description

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

server	DMS JIRA

ImplementedLast WorkingTestedStatus

columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-868

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

903

869

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

911

870

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

910

872

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

903

883

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

913

1066

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

905

998

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

909

1077

________________________

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

918

896

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

921

897

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

880

898

Sprint 43

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

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
Automatic proposal to panel assignment based on Science Category
Delete reviewers
SRP members can only belong to one panel
Assign multiple chairs

Status

title

subtle	True
colour	Yellow
color	green

not

Not implemented

feasibility groups

Status


subtle	True
colour	Red
color	green
title	to fix

SRP Chair

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.

Finalize Review Configuration

Finalize can occur when
- all proposals are vetted
- the Solicitation is Closed
In line prompt to confirm Finalization
Finalizing should prevent future edits to configuration.

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

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

1167

884

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

912

889

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

908

1412

Sprint 45

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

Finalize can occur when
- all proposals are vetted
- the Solicitation is Closed
Finalizing should prevent future edits to configuration.
Pop-up asking to confirm Finalization

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,

JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,

type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1168

Configuration and Vetting is part of the Proposal Process Tab

PPRs - Conflict Declaration

Description	JIRA	Implemented	Last Working	Tested	Status
Auto Conflicts based on authorship Instructions present Submit & Certify button is always there but not active until necessary Highlights when option selected to keep track of progress

914

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

1055

884

status

Sprint 45

subtleTruecolourBluecolorgreentitleWorking

Sprint 61

V0.2

Sprint 61

V0.2

Status

colour

subtle	True

Yellow

title
Blue
color	green

not implemented

Working

status

subtleTruecolourRedcolorgreentitleto 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

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 must 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)
A valid certifications is one without a state of unknown and with comments if conflicted.
Certifying conflicts updates UI widgets that show "Certified" status
- Individual Review list
- Summary UI

Jira

server	DMS

serverDMS

JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

933

885

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

904 StatussubtleTruecolourBluecolorgreentitleWorking StatussubtleTruecolourYellowcolorgreentitlenot implemented StatussubtleTruecolourRedcolorgreentitleto fix

OSR Reviews

DescriptionJIRAImplementedLast WorkingTestedStatus

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

875

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

925

1413

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

924

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-923

JiraserverDMS JIRAcolumnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution

1414

Sprint 46

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

Must complete Conflicts before progressing to ISRs
Cannot change Auto Conflict
Default Conflict state is Unknown
Reviewer must change to either Conflict or Available
Can view Conflict State per ISR
Can see Proposal ID, Abstract, and Title
Bulk Action of Certification (cannot certify some and not others)
A valid certifications is one without a state of unknown and with comments if conflicted.
Certifying conflicts updates UI widgets that show "Certified" status
- Individual Review list
- Summary UI

Status


subtle	True
colour	Red
color	green
title	to fix

SRP Chair

must complete conflicts like a reviewer

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,

columnskey,summary,type,created,updated,due,

assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-

1175Sprint 43Sprint 43Sprint 43 StatussubtleTruecolourBluecolorgreentitleWorking

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

887

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-871

Sprint 46/47

Sprint 61

V0.2

Sprint 61

V0.2

StatussubtleTruecolourYellowcolorgreentitlenot implementedHard to tell which proposals have been reviewed.

Status

colour

subtle	True

Red

title
Blue
color	green

to fix

Score needs to be binary

Version 0.3 Outline

Working

must complete conflicts like a 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
Conflicted ISRs do not go to Consensus

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-886

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1146

Sprint 45/47

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

Can update Conflict state and Certify (preferable that it is done after user certifies)
Conflicted ISRs do not go to Consensus

PPRs - Review Type Assignments

Description

JIRA

Implemented

Last Working

Tested

Status

SRP Chair

can see a "matrix" of Reviewers in their panel, their Conflict States, the Review States of their ISRs
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
Cannot be able to assign types of Conflicted reviewers
Can change Review Type of External Reviewer
External Reviewer's name is redacted but can see the Review Type and Review State for the external ISR
Can upload a configuration file
Proposal ID, Proposal Title, Pop-out to Proposal

Sprint 46/47

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

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.
Cannot assign Review Types to a conflicted reviewer
Can change Review Type of External Reviewer
External Reviewer's name is redacted but can see the Review Type and Review State for the external ISR

Status


subtle	True
colour	Yellow
color	green
title	not implemented

Can upload a configuration file

TTA Member

Can change any Review Type even if the Review State is Finalized until Consensus starts
Can change the Review Type of external ISRs until Consensus of the hosting panel begins
Can upload a configuration file

Sprint 45/47

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

Can change RT of external ISR as long as Consensus for the hosting panel has not started
Can change RT of any ISR even in Finalized State until the start of Consensus

Status


subtle	True
colour	Yellow
color	green
title	not implemented

Can upload a configuration file

PPRs - ISRs

Description

JIRA

Implemented

Last Working

Tested

Status

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
Cannot provide comments or scores for ISRs with a Review State of Closed
Edge cases:
- 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.
Instructions present
Finalize Reviews button always there but not active

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-877

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-878

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-873

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-879

Sprint 46, 47

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

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

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.
Cannot provide comments or scores for ISRs with a Review State of Closed
Instructions present
Finalize Reviews button always there but not active

Status


subtle	True
colour	Red
color	green
title	to fix

External Reviewer

External Reviewer is someone who is on any one panel associated with the Solicitation in question
An external reviewer can be assigned an external ISR for any proposal as long as the Panel associated with that proposal has not started Consensus
An external reviewer can be assigned an ISR even if their host panel is in Consensus.
External Reviewers do not have to declare conflicts on external ISRs. When assigned, the conflict state is automatically set to Available
External Reviewers can see the external ISR in their list of ISRs.
ER can provide comments, scores, save, complete, and finalize their external ISRs
ER do not have access to the Consensus UI or any responsibility at Consensus for the panel associated with the external ISR.
ER scores and comment are available in Consensus and correctly integrated

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1395

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1328

Sprint 59

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

External Reviewer is someone who is on any one panel associated with the Solicitation in question
An external reviewer can be assigned an external ISR for any proposal as long as the Panel associated with that proposal has not started Consensus
External Reviewers do not have to declare conflicts on external ISRs. When assigned, the conflict state is automatically set to Available
ER do not have access to the Consensus UI or any responsibility at Consensus for the panel associated with the external ISR.
ER scores and comment are available in Consensus and corretly integrated

External Reviewers can see the external ISR in their list of ISRs.
ER can provide comments, scores, save, complete, and finalize their external ISRs
An external reviewer can be assigned an ISR even if their host panel is in Consensus.

Status


subtle	True
colour	Red
color	green
title	to fix

Import/Export ISRs

a CSV file is expected but it can use as a delimiter any of the following:
- , ; | tab
putting double quotes around the comment will keep the commas within the comment safe
if reviews exist when asked to export, it will export the reviews
cannot upload a file with any blank fields (fails and warning issued)
if a user changes the name of the reviewer within the file, it gives an error
protects against Bobby Drop Tables
on a successful upload, the Review State of the ISR will changed to Saved
reuploading will update the comments/score
Don't need every ISR in file to work

Sprint 57?

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	working

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)
can change Review Type until Consensus is initated for the SRP member's panel.
can change Review State until Consensus is initiated for the SRP member's panel.

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1039

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	working

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
an 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)
- 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
can change Review Type until Consensus is initated for the SRP member's panel.
can change Review State until Consensus is initiated for the SRP member's panel.

Status


subtle	True
colour	Yellow
color	green
title	not implemented

A separate Close functionality will be per ISR

Status


subtle	True
colour	Red
color	green
title	to fix

Adding external reviewers as TTA member

If an external reviewer is added, the Conflict state is automatically Available.
TTA member can change Review Type until Consensus starts

Sprint 59

Sprint 61

V0.2

Sprint 61

V0.2

PPRs - Consensus

Description

JIRA

Implemented

Last Working

Tested

Status

SRP Member

As a conflicted SRP member, only see the SRP scope, proposal ID, title, abstract, scores, and Rank
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
- Rank
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 only for now.
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
Warning them Completing Consensus
Badges display Review Types/ Conflicts
~~Import/Export Consensus Comments~~
Badges display all reviewer roles
Does not display other conflicts

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-903

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-911

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-910

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-903

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-913

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-905

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-909

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-918

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-921

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-880

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1415

Sprint

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	working

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.
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 only for now.
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
Warning them Completing Consensus
Badges display Review Types/ Conflicts
~~Import/Export Consensus Comments~~
Badges display Review Types/ Conflicts

Status


subtle	True
colour	Yellow
color	green
title	not implemented

Status


subtle	True
colour	Red
color	green
title	to 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 complete and finalize Consensus Reviews
- Note, there is not a bookkeeping equivalent to "completed" from ISRs for SRP Chairs in this process
Warning on Finalizing and Completing Comments
Cannot see Conflicted comments and FNIS
History of Changes of Consensus Reviews to be kept
Can see all Reviewers by Review Type (badges with P,S, T, all T) and all Conflicted
Scores shown to 100ths place

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1167

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-912

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-908

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-914

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1055

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

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 complete and finalize Consensus Reviews
- Note, there is not a bookkeeping equivalent to "completed" from ISRs for SRP Chairs in this process
Warning on Finalizing and Completing Comments
Cannot see Conflicted comments and FNIS
Can see all Reviewers by Review Type (badges with P,S, T, all T) and all Conflicted
Consistent display of SRP Score and Mean score when appropriate

Status


subtle	True
colour	Yellow
color	green
title	not implemented

History of Changes of Consensus Reviews to be kept

Status


subtle	True
colour	Red
color	green
title	to fix

External ISRs

Comments and Scores from External ISRs are shown and properly integrated into FNIS
External reviewers names are redacted for all but the TTA member. Instead, any reference to them is given as "External Reviewer"

Sprint 59

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

name of external reviewers redacted in badges for review types

Comments and scores properly integrated

TTA Member

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

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-933

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-904

Sprint 59

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

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

Status


subtle	True
colour	Yellow
color	green
title	not implemented

Status


subtle	True
colour	Red
color	green
title	to fix

Uploading PPR Proposal Reviews (Removed)

As SRP

download contains all review comments for the panel
uploading must only contain proposals that are RT = P/S (and not conflicted).
Cannot modify SRP Score in an upload
Fails if any others are included.

OSR Reviews

Description

JIRA

Implemented

Last Working

Tested

Status

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

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-925

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-924

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-923

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1175

Sprint 43

Sprint 61

V0.2

Sprint 61

V0.2

Status


subtle	True
colour	Blue
color	green
title	Working

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).
Score needs to be binary

Status


subtle	True
colour	Yellow
color	green
title	not implemented

Status


subtle	True
colour	Red
color	green
title	to fix

Review Process Simulation Tools

Description

JIRA

Slice 1

Future improvements

Solicitation

Specify name of Solicitation
Specify Capabilities in Solicitation
Set Execution and Call period

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1437

Uses existing Solicitation generator (Sem25A)
Separate Solicitation and Proposal Generation
Give Solicitation Name, Proposal Process
Set as Demo/Test

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1470

Upload JSON for Solicitation Configuration
Demo data

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1453

Proposal Generation

specify number of proposals
use capabilities defined in Solicitation to generate demo/test proposals
Realistic Demo or Test proposals
can generate 100 proposals at a time and randomly distributes them across science categories

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1437

Uses existing generator paired with Solicitations
Proposals are belong to 1 category
Simple proposals - no real allocation requests
Science Categories from Solicitation
Expanded user database

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1466

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1546

More realistic proposals
limited to 100 proposals generated at a time.
- it we have to do 1500, that will be a lot of waiting

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1453

Close Solicitation

Use existing structure

Panel Configuration

Create SC based on SCs of proposals
- Set Name, Science Category
Associate users with SRP
Specify a chair
Associate proposals with SCs

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1436

Create 1 panel → 10 panels
Assign SC
Assign each a unique Science Category
Fill 6 non TTA members
Assign Chair
Assign Proposals

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1313

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1545

Vetting

Vet all proposals automatically

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1436

Vet all proposals without modification

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1312

Finalize Panel Configuration

use existing framework; hookup FE

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1471

Conflicts

Fill out Conflict Declarations
Certify
Per panel, per SRP? Bulk options

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-901

Per panel button
set all to Available unless AutoConflicted
Certify Conflicts

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1472

ISRs

Assign Review Types satisfying minimum SRsPerProposal and 1 Primary and 1 Secondary per proposal
If assigned P,S,T, fill out comments and score randomly
If test solicitation, the comments should state the Proposal ID, the individual score, the reviewer name, and Review Type of reviewer
If Demo solicitation, the comments should be simulated comments.
Per panel, per reviewer, bulk options?

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-901

Per panel button
Use pattern for comments for all ISRs
- Review Type not None
- Review State not Blank
Randomize score
Assign Review Types randomly
- 1 primary
- 1 secondary
- 1 tertiary

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1473

Finalize ISRs

per panel, per reviewer, bulk options?

per panel button to finalize ISRs

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1474

Initiate Consensus Phase

hook up existing structure per panel

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1475

Consensus

Fill out Comments for each
Complete PPR

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-901

Use appended ISR comments to make PPR Proposal Process comments for PI
Complete Reviews per panel
Pattern internal comments

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1476

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1477

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1551

Finalize PPR

per panel

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1478

Simulate All

Simulate full PPR Review Process

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1547

More realistic Simulated Proposals

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1466

Description

Requirement

Implementation for v0.2.2

Title

More than 20 characters

Simulated Proposal N for Test Solicitation

Abstract

More than 10 characters

Lorem ipsum

Authors

not a TTA member

Any user not a TTA member

Scientific Justification

pdf less than 4 pages

Stopgap PDF

Science Category

One SC

Select from Solicitation definition

Allocation Requests

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1617

Create 1 to 3 Allocation Requests and randomly select the Facility from the ones defined in the Solicitation.

restricted to VLA, GBT

Capability Request per Allocation Request

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1616

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1618

Per Allocation Request, create 2 to 10 Capability Requests. The Capability should be randomly selected from what is available for the Facility in the Solicitation.

restricted to VLA Continuum, GBT Spectral Line

Field Sources per Capability Request

Per Capability Request, randomly select 1 Test Field Sources available to the Capability.

Use calibratorList.json to select 1 field source + spectral spec pairs per Capability Request

If VLA Continuum

set other parameters to 0 if not specified in json

If GBT Spectral Line

set Peak Line Flux Density to 10% of peak continuum flux density
set Line Width to 50 km/s
set other parameters to 0 if not specified in json

Spectral Specifications per Capability Request

Per Capability Request, randomly select between 1 Test Spectral Specifications available to the Capability.

see above for center frequency

If VLA Continuum

set spectral resolution 1000 km/s
set bandwidth to 2000 km/s

If GBT Spectral Line

set spectral resolution to 10 km/s
set bandwidth to 300 km/s

Performance parameters per Capability Request

Per Capability Request, set Test Performance Parameters

If VLA Continuum:

randomly select a desired VLA Configuration from the ones available in the Capability (A, B, C, D), once a config is selected B_max and B_min is defined
- B_max = (36.4, 11.1, 3.4, 1.03) km
- B_min = (0.68,0.21,0.035,0.035) km
calculate Angular Resolution as
θ = 1.2(c_km/freq_Hz)/B_max where
c is the speed of light = 2.998e5 km/s
calculate largest angular scale as
θ = (c_km/freq_Hz)/B_min where
set RMS sensitivity as 10% of the peak continuum flux density

If GBT Spectral Line

calculate the Angular Resolution as
θ = 1.2(c_km/freq_Hz)/D
where D = 0.1 km
set RMS Sensitivity as 30% of the peak line flux density

Calibration parameters per Capability Request

Per Capability Request, randomly select a Test Calibration Parameter

If VLA Continuum:

randomly set Polarization Calibration boolean to True

If GBT Spectral Line:

randomly set Flux Density Calibration to True
randomly set Test Source to True
randomly set Polarization Calibration to True

Fake Feasibility Reviews

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1762

Pattern

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)

Description

JIRA

Implemented

Last Working

Tested

Status

Scientific Justification

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-935

<Sprint 32

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	true
colour	Green
color	green
title	working

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

General Allocation Request

<Sprint 32

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Can Select a Facility

Can add one or more AR

Can delete AR

Can rename

General Capability Requests

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-845

< Sprint 32

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	true
colour	Green
color	green
title	working

Can Delete

Can Add Multiples

Can Rename

Import Field Sources, Spectral Specs

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-940

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-938

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-966

Sprint 30

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	true
colour	Green
color	green
title	working

Zeros import.

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

There are units on the headers at import

Status


subtle	true
colour	Grey
color	green
title	Ignored

HMS DMS doesn't import

Units not enforced on widget

Field Source and Spectral Specs

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-939

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-937

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-948

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-952

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1003

< Sprint 30

Status


subtle	True
colour	Green
color	green
title	test

Sprint 38

Status


subtle	True
colour	Blue
color	green
title	prod

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	true
colour	Green
color	green
title	working

Zeros persist in fields

Entries persists

Status


subtle	true
colour	Red
color	green
title	bug

Negative Values in Dec DMS entry do not display correctly

Status


subtle	True
colour	Grey
color	green
title	Ignore for release

Units on fields

Precision

Status


subtle	True
colour	Grey
color	green
title	configuration 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 32

Sprint 37.3

Status


subtle	true
colour	Green
color	green
title	working

Calibration Parameters

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-942

Sprint 32

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	true
colour	Green
color	green
title	working

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

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-941

Sprint 32

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	true
colour	Green
color	green
title	working

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

Advanced Tab

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-949

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-941

Jira

showSummary	true
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-975

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-973

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-992

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-993

Sprint 36

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	true
colour	Green
color	green
title	working

Filtering Works as expected

Units exist on fields

Angular Resolution is present for VLA

Import Widget has units

Status


subtle	True
colour	Red
color	green
title	bug

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

Status


subtle	True
colour	Yellow
color	green
title	Review

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

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-951

Sprint 32

Sprint 37.3

Status


subtle	True
colour	Grey
color	green
title	hack 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

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-977

Sprint 30

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	True
colour	Grey
color	green
title	hack for release

working but not scientifically checked

Editing Observation Specification

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-945

< Sprint 30

Sprint 37.4

Status


subtle	true
colour	Green
color	green
title	working

Can add by target

Can add by Hardware (Simple)

Moving Scans works as expect

General Observation Specification

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-943

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-946

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-952

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-1005

Sprint 32

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	true
colour	Green
color	green
title	working

Times in tabs and summary are reporting consistently

Filtering works

Status


subtle	True
colour	Grey
color	green
title	Ignore for release

Precision on entries

Status


subtle	True
colour	Red
color	green
title	bug

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


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status


subtle	True
colour	Green
color	green
title	test

Sprint 39

Status


subtle	True
colour	Blue
color	green
title	prod

v0.1.2

Status

subtle	true
color	green
title	working

Version Reports

Expand

title	version 0.1 report

Landing Page

Updated 10.12.22 for sprint 39, v0.1.2

Description

JIRA

Implemented

Last Working

Tested

Status

Message of the Day on landing page

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-754

Sprint 34

Sprint 37

Status

subtle	True
color	green
title	working

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

Solicitation Creation

Description

JIRA

Implemented

Last Working

Tested

Status

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

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-342

Solicitation Config Files

Sprint 16

Sprint 30

Status


subtle	True
colour	Grey
color	green
title	hack for release

Configure Field Source, SS, PP, CP

Status


subtle	True
colour	Blue
color	green
title	not implemented

Configure Advance Tab options

Status


subtle	True
colour	Blue
color	green
title	not implemented

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

Status


subtle	True
colour	Blue
color	green
title	not implemented

Solicitation Tab

Sprint 37.3

Only available to TTA Member

Description

JIRA/Behavior

Implemented

Last Working

Tested

Status

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

in a list
in a detailed view (Card)

<Sprint 29

Sprint 37

Status


subtle	true
colour	Green
color	green
title	working

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

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-976

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

Status


subtle	True
colour	Yellow
color	green
title	Review

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

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-976

Status


subtle	True
colour	Yellow
color	green
title	Review

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

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-972

<Sprint 35

Sprint 37.5

Status


subtle	true
colour	Green
color	green
title	working

Navigate and Edit OS on fresh AR

Not Implemented

Status


subtle	True
colour	Grey
color	green
title	ignored for release

Create Proposal

Capability (General)

Description

JIRA

Implemented

Last Working

Tested

Status

Scientific Justification

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-935

<Sprint 32

Sprint 37.4

Status


subtle	true
colour	Green
color	green
title	working

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 32

Sprint 37.4

Modify text or remove entirely

Can Select a Facility

Can add one or more AR

Can delete AR

General Capability Requests

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-845

< Sprint 32

Sprint 37.4

Status


subtle	true
colour	Green
color	green
title	working

Can Delete

Can Add Multiples

Import Field Sources, Spectral Specs

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-940

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-938

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-966

Sprint 30

Sprint 37.4

Status


subtle	true
colour	Green
color	green
title	working

Zeros import.

Widget matches well to headers

There are units on the headers at import

Status


subtle	true
colour	Grey
color	green
title	Ignored

HMS DMS doesn't import

Units not enforced on widget

Field Source and Spectral Specs

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-939

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-937

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-948

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-952

< Sprint 30

Sprint 37

Status


subtle	true
colour	Green
color	green
title	working

Zeros persist

Negative Numbers work as expected

Status


subtle	True
colour	Grey
color	green
title	Ignore for release

Units on fields

Precision

Selection of Calibration Parameters affects STL and OS

Sprint 32

Sprint 37.3

Status


subtle	true
colour	Green
color	green
title	working

Calibration Parameters

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-942

Sprint 32

Sprint 37.4

Status


subtle	true
colour	Green
color	green
title	working

Performance Parameters

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-941

Sprint 32

Sprint 37.4

Status


subtle	true
colour	Green
color	green
title	working

Advanced Tab

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-949

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-941

Jira

showSummary	true
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-975

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-973

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-992

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-993

Sprint 36

Sprint 37.4

Sprint 37.5

Status


subtle	true
colour	Green
color	green
title	working

Filtering Works as expected

Units exist on fields

Angular Resolution is present for VLA

Import Widget has units

Status


subtle	True
colour	Red
color	green
title	bug

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

Status


subtle	True
colour	Yellow
color	green
title	Review

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

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-951

Sprint 32

Sprint 37.3

Status


subtle	True
colour	Grey
color	green
title	hack 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

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-977

Sprint 30

Sprint 37.3

Sprint 37.4

Status


subtle	True
colour	Grey
color	green
title	hack for release

working but not scientifically checked

Editing Observation Specification

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-945

< Sprint 30

Sprint 37.4

Status


subtle	true
colour	Green
color	green
title	working

Can add by target

Can add by Hardware (Simple)

Moving Scans works as expect

General Observation Specification

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-943

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-946

Jira

showSummary	false
server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01
key	STT-952

Sprint 32

Sprint 37.5

Status


subtle	true
colour	Green
color	green
title	working

Times in tabs and summary are reporting consistently

Filtering works

Status


subtle	True
colour	Grey
color	green
title	Ignore for release

Precision on entries

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

<Sprint 32

Sprint 37.4

Status

subtle	true
color	green
title	working

Misc

Expand

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

...

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 123

New Version Current

Key

Summary of Available Solicitations, Facilities, and Capabilities

Helpful Files for Testing

Current Report

Easy Navigation to Jira Epics and Sprints

Notifications

Solicitation Creation

Navigation

Current Report

Landing Page

Notifications

PPRs

PPRs - Vet Proposals

Solicitation Creation

Navigation

Submission

PPRs - Conflict Declaration/ Role Assignments

PPRs - ISRs

PPRs

PPRs - Vet Proposals

PPRs - Review Configuration

PPRs - Conflict Declaration

OSR Reviews

Version 0.3 Outline

PPRs - Review Type Assignments

PPRs - ISRs

PPRs - Consensus

OSR Reviews

Review Process Simulation Tools

More realistic Simulated Proposals

Create Proposal

Capability (General)

Version Reports

Landing Page

Solicitation Creation

Navigation

Create Proposal

Capability (General)

Misc