Versions Compared

Old Version 197

changes.mady.by.user Allison Costa

Saved on

compared with

New Version Current

changes.mady.by.user Allison Costa

Saved on

Key

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

Updated 1102.0801.23 2024

Detailed TTA Tools Sprint Feedback Page

...

Table of Contents
outlinetrue

Summary of Available Solicitations, Facilities, and Capabilities

...


Section
Column


Solicitations for review

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

Sprint 37

Gone after Sprint 37

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

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

20D

Sprint 37

Gone after Sprint 37

Specific Hardware Constraints:

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

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

Sem_25ASprint 38 - current, prod v0.1.2

VLA and GBT have L – Q band available

Production Solicitation for v0.1

SC_GBT_24BSprint 38 - current, prod v0.1.2

GBT only, L, S, and C band

Production Solicitation for v0.1

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

Column
Solicitation Specific Facility/Capability for testing


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

Prototype FE stories:

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

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

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

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

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




Helpful Files for Testing


FileUpdatedIntended CapabilityDescription

GBTmegamaser_FS_50.csv

Sprint 38GBT Spectral Line50 Field Sources from the Megamaser use case; the use case specifics a  rms line sensitivity of 6 mJy

GBTmegamaser_SS_1.csv

Sprint 38GBT Spectral Line1 Spectral Spec from Megamaser use case; Units are GHz, km/s, km/s (extra spectral spec but can delete)

GBTSpectralLine_SS_2.csv

Sprint 38GBT Spectral Line

General GBT Spectral Line SS.

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

VLAContinuum_FS_2.csv

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

VLAContinuum_SS_2.csv

Sprint 38VLA Continuum

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

VLA_SS_allbands.csv

GBT_SS_allbands.csv

FieldSources_3_VLA.csv

FieldSources_3_GBT.csv

Sprint 39

v0.1.2

VLA Continuum

GBT Spectral Line

General Test Files


Easy Navigation to Jira Epics and Sprints

NameJiraDescription

Sprint 48

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

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

Feb 28

Sprint 49

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

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

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

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

Jira
serverDMS JIRA
jqlQuerysprint = 161
counttrue
serverIdeb2e750b-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
serverDMS JIRA
jqlQuerysprint = 162
counttrue
serverIdeb2e750b-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

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

Refactoring 1/?
Sprint 54

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

Refactoring 2/?
Sprint 55

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

Refactoring 3/?
Sprint 56

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

Refactoring 4/?
Sprint 57

Sprint 58

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

connecting FE/BE consensus. System fully connected
Sprint 59

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

bug hunting and final feature push
Sprint 60

Jira
serverDMS JIRA
jqlQueryissueKey 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)
counttrue
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01

bug hunting and final feature push
Sprint 61

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

bug hunting; final official sprint of version 0.2
Sprint 62

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

prototype v0.2.1 interface; RIDs for internal view
SRP Process

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

Epic
SRP Configuration

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

Epic
OSR

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

Epic
Proposal Submission

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

Epic

Feasibility Reviews

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

Epic
V0.2 Bugs

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

Epic
Solicitation Configuration

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

Epic
Proposal Bugs

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

Epic
Label: NotificationRelated

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

Label
Label: ConsensusReview

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

Label

Label: Conflicts

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

Label
Label: Configurability

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

Label
Label: ISR

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

Label
Label: TTAMember

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

Label
Label: SRPChair

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

Label


Current Report

Landing Page

...

DescriptionJIRAImplementedLast WorkingTestedStatus
  • Message of the Day on landing page

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


Sprint 34Sprint 37Sprint 37

Status
subtleTrue
colorgreen
titleworking

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



Notifications

DescriptionJIRAImplementedLast WorkingTestedStatus

Notification for a Submitted Proposal

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

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



Sprint 47

Sprint 6168

V0.2

Sprint 6168

V0.2

Status
subtletrue
colourGreen
colorgreen
titleworks

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

Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

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


Notification when Review Configuration is Finalized

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

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

Sprint 47

Sprint 6168

V0.2

Sprint 6168

V0.2

Status
subtletrue
colourGreen
colorgreen
titleWorking

  • 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
subtleTrue
colourBlue
colorgreen
titlenot implemented

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


Notification when TTA Member changes Conflict State of Reviewer

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

Sprint 47

Sprint 6168

V0.2

Sprint 6168

V0.2

Status
subtletrue
colourGreen
colorgreen
titleWorking

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

Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

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

Status
subtleTrue
colourYellow
colorgreen
titleReview

  • The ticket says that "Conflict Reason, and updated Conflict State" should be included in email but it is currently not
  • right now, 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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-914




Status
subtletrue
colourYellowGreen
colorgreen
titleto testWorking

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


Notification when all ISRs are finalized for a panel

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

Sprint 50

Sprint 6168

V0.2

Sprint 6168

V0.2

Status
subtletrue
colourGreen
colorgreen
titleWorking

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

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

Sprint 50

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtletrue
colourGreen
colorgreen
titleWorking

  • 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

...

DescriptionJIRAImplementedLast WorkingTestedStatus

Create a Simple Solicitation from JSON for

  • VLA
  • GBT

not implemented/requirements not in a story:

  • modify parameters such as frequency ranges on bands

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

Solicitation Config Files


Sprint 16Sprint 16Sprint 30

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

Configure Field Source, SS, PP, CP





Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

Configure Advance Tab options





Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

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



 

Status
subtleTrue
colourBlue
colorgreen
titlenot implemented
Solicitation Tab

Sprint 61

V0.2

Sprint 61

V0.2

Only available to TTA Member

A Proposal Prefix can be specified per solicitation

 

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

Sprint 40Sprint 40Sprint 40

Status
subtleTrue
colourBlue
colorgreen
titleWorking

Create a Test Solicitation+Test Proposals
Sprint 46


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

Close Solicitation

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

Sprint 45

Sprint 61

V0.2

Sprint 61

V0.2

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



Navigation

...


DescriptionJIRA/BehaviorImplementedLast WorkingTestedStatus

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

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

<Sprint 29Sprint 37Sprint 37

Status
subtletrue
colourGreen
colorgreen
titleworking

Status
subtleTrue
colourYellow
colorgreen
titleReview

  • would like to filter on proposals by Science Category


Saving within a CR

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

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





Status
subtleTrue
colourGreen
colorgreen
titleworking

Saving and AR

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

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




Status
subtleTrue
colourGreen
colorgreen
titleworking

Observation Specification Generation

Prompt warns that user is overwriting their OS.

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

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

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

<Sprint 35Sprint 38Sprint 38

Status
subtletrue
colourGreen
colorgreen
titleworking

Navigate and Edit OS on fresh AR



Not Implemented

Status
subtleTrue
colourGrey
colorgreen
titleignored for release

Review Tab
Sprint 43

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

Can see panels once Review Configuration is Finalized

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

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

TTA Member can see both SRP and Chair views

Submission

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


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

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

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


Sprint 41Sprint 43Sprint 43

 

Status
subtleTrue
colourGreen
colorgreen
titleworking

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

Observatory Copy and Author Copy

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

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

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

Sprint 42Sprint 42Sprint 42

Status
subtleTrue
colourGreen
colorgreen
titleworking

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

Status
subtleTrue
colourRed
colorgreen
titlebug

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

Status
subtleTrue
colourYellow
colorgreen
titlereview

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

Status
subtleTrue
colourRed
colorgreen
titlebug

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


Proposal State Changes

Allowed:

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

Not Allowed:

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

Sprint 42SprintSprint 42

Status
subtleTrue
colourGreen
colorgreen
titleworking

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

Status
subtleTrue
colourRed
colorgreen
titlebug

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

Status
subtleTrue
colourYellow
colorgreen
titleReview

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

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

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

Sprint 52

Status
subtleTrue
colourGreen
colorgreen
titleworking

Back end supports printable view

Status
subtleTrue
colourYellow
colorgreen
titleReview

Navigation to this functionality missing in UI

Status
subtleTrue
colourRed
colorgreen
titlebug

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

...

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.
  • 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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-874

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

Sprint 44

Sprint 61

V0.2

Sprint 61

V0.2

 

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • 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
subtleTrue
colourRed
colorgreen
titleto fix

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


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




PPRs - Review Configuration

...

DescriptionJIRAImplementedLast WorkingTestedStatus

Panels

  • Create SRP panels with unique names
  • Delete SRP Panels
  • Associate panels with 1 or more Science Categories (edge cases)
  • Assign 1 or more SRP Chairs
  • Assign multiple 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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-867

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

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

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

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

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

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

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

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

________________________

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

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

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

Sprint 43

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • can create new SRP panels
  • can select from a pre-set list of SRP panels
  • can assign SRP members/chair
  • can assign proposals to SRP
  • Automatic proposal to panel assignment based on Science Category
  • Delete reviewers
  • SRP members can only belong to one panel
  • Assign multiple chairs

 

Status
subtleTrue
colourYellow
colorgreen
titleNot implemented

  • feasibility groups

Status
subtleTrue
colourRed
colorgreen
titleto fix

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



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.


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

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

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

Sprint 45

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

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




Configuration and Vetting is part of the Proposal Process Tab



PPRs - Conflict Declaration

DescriptionJIRAImplementedLast WorkingTestedStatus
  • 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


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

Sprint 45

Sprint 61

V0.2

Sprint 61

V0.2

 

Status
subtleTrue
colourBlue
colorgreen
titleWorking

 

SRP Reviewer

  • Must complete Conflicts before progressing to ISRs
  • Cannot change Auto Conflict
  • Default Conflict state is Unknown
  • Reviewer must change to either Conflict or Available
  • Reviewer 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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-885

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

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

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

Sprint 46

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • Must complete Conflicts before progressing to ISRs
  • Cannot change Auto Conflict
  • Default Conflict state is Unknown
  • Reviewer must change to either Conflict or Available
  • 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
subtleTrue
colourRed
colorgreen
titleto fix

SRP Chair

  • must complete conflicts like a reviewer

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

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

Sprint 46/47

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

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

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

Sprint 45/47

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • 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

DescriptionJIRAImplementedLast WorkingTestedStatus

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
subtleTrue
colourBlue
colorgreen
titleWorking

  • 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
subtleTrue
colourYellow
colorgreen
titlenot 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
subtleTrue
colourBlue
colorgreen
titleWorking

  • 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
subtleTrue
colourYellow
colorgreen
titlenot implemented

  • Can upload a configuration file

PPRs - ISRs

DescriptionJIRAImplementedLast WorkingTestedStatus

SRP Reviewer

  • See list of proposals (after conflict certification)
  • Review Type is displayed
    • Default is None; otherwise P,S,T
  • Review State is displayed
    • default is Blank; otherwise Saved, Completed, Finalized, Closed
  • Conflict State is displayed
    • Conflict/Available
  • If not Conflicted, have an ISR in which to enter comments and a score and see the proposal
    • can Save (Review State → Saved) per ISR
      • validate if score not equal to 0; otherwise it cannot save
      • does not validate comments
    • can Complete (Review State → Completed) per ISR
    • can Finalize (bulk action) if any ISRs with Review not equal to None are not Closed or Finalized
  • If Conflicted, only see title, abstract, proposal ID and cannot enter any information
  • All comments and scores are saved (though not propagated to consensus; see later)
  • Normalized Individual Scores are calculated on Finalize
  • 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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-877

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

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

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


Sprint 46, 47

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • 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
subtleTrue
colourRed
colorgreen
titleto 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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1395

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

Sprint 59

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • 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
subtleTrue
colourRed
colorgreen
titleto 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
subtleTrue
colourBlue
colorgreen
titleworking

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


Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleworking

  • 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
subtleTrue
colourYellow
colorgreen
titlenot implemented

  • A separate Close functionality will be per ISR

Status
subtleTrue
colourRed
colorgreen
titleto 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

DescriptionJIRAImplementedLast WorkingTestedStatus

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

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

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

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

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

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

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

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

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

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

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

Sprint

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleworking

  • 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
subtleTrue
colourYellow
colorgreen
titlenot implemented

Status
subtleTrue
colourRed
colorgreen
titleto fix



SRP Chair

  • Overview of consensus comment state (Completed, Saved)
  • Overview of Review Types and Conflict State
  • Ability to change SRP Score directly
  • Update Finalized Normalized Individual Scores
    • Forces update to MNS, STD_MNS, and SRP if the SRP score was not manually changed already
  • Have visibility to past disposition letters
  • Review Consensus comments, modify comments, and 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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1167

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

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

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

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



Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

  • 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
subtleTrue
colourYellow
colorgreen
titlenot implemented

  • History of Changes of Consensus Reviews to be kept

Status
subtleTrue
colourRed
colorgreen
titleto 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
subtleTrue
colourBlue
colorgreen
titleWorking

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

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

Sprint 59

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

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

Status
subtleTrue
colourYellow
colorgreen
titlenot implemented

Status
subtleTrue
colourRed
colorgreen
titleto 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

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


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

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

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

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

Sprint 43

Sprint 61

V0.2

Sprint 61

V0.2

Status
subtleTrue
colourBlue
colorgreen
titleWorking

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

Status
subtleTrue
colourYellow
colorgreen
titlenot implemented

Status
subtleTrue
colourRed
colorgreen
titleto fix

 

Review Process Simulation Tools

subtle
  • Set as Demo/Test

DescriptionJIRASlice 1Slice 2Future improvements

Solicitation

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

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

 

 

 

  • Uses existing Solicitation generator (Sem25A)
  • Separate Solicitation and Proposal generatorGeneration
  • Give Solicitation Name, Proposal Process, Number of Proposals
Status
True
colourGreen
colorgreen
titlein progress
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1470

 


 

  • Separate Solicitation and Proposal Generation
  • Upload JSON for Solicitation Configuration
  • Demo data

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

  • Separate Solicitation and Proposal Generation
  • More realistic proposals
  • Science Categories from Solicitation
  • Expanded user database
  • limited to 100 proposals generated at a time.
    • it we have to do 1500, that will be a lot of waiting

1466

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

  • 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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-
1546
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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1436

 


 

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

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

  • Create 1 to 6 panels
  • Assign each a unique Science Category

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


 

Vetting

  • Vet all proposals automatically

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

 


  • Vet all proposals without modification

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


Finalize Panel Configuration


  • use existing framework; hookup FE

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


Conflicts

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

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

 


  • Per panel button
  • set all to Available unless AutoConflicted
  • Certify Conflicts

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-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
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-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 secondardsecondary
    • 1 tertiary

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



Finalize ISRs

per panel, per reviewer, bulk options?


  • per panel button to finalize ISRs

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


Initiate Consensus Phase


  • hook up existing structure per panel

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


Consensus

  • Fill out Comments for each
  • Complete PPR

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

 

 

 

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

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

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

  • Pattern internal comments

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



Finalize PPR


  • per panel

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


Simulate All


  • Simulate full PPR Review Process
  • Jira
    serverDMS JIRA
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
    keySTT-1547





More realistic Simulated Proposals

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

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

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

Create 1 to 3 Allocation Requests and randomly select the Facility from the ones defined 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.

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

per Allocation Request

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

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-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 Calibration parameters per Capability Request

Per Capability Request, randomly select a Test Calibration Parameter1 Test Field Sources available to the Capability.

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

If VLA Continuum:

  • randomly set Polarization Calibration boolean to Trueother parameters to 0 if not specified in json

If GBT Spectral Line:

  • randomly set Peak Line Flux Density Calibration to True
  • randomly set Test Source to True
  • randomly set Polarization Calibration to True

Version 0.3 Outline

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

Pattern

DescriptionJIRASlice 1 - v0.2.2Slice 2 v0.2.2

Scheduler

  • Source Conflict identification

Scheduler Tools

  • 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

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

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

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

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

  • Version Structure
    • Create Allocation Dispositions
      • Jira
        serverDMS JIRA
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
        keySTT-1565
    • Create Observation Specification Dispositions
      • Jira
        serverDMS JIRA
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
        keySTT-1566
    • Create Available Time Model
      • Jira
        serverDMS JIRA
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
        keySTT-1564
  • Assign Priorities
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1657
  • Change AD state
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1658
  • Provide Comments
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1575
  • Publish to TAC
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1568
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1570
  • Publish to Directors Review
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1569
  • UI Prototype (Schedulers Tools)
    • Summary view for Allocation Versions and deployment to TAC/DR
    • Spot for Proposal Information (AR/OSs/Metadata/Scientific Justification)
    • Spot for Proposal Review
    • Spot for Feasibility Review
    • Spot for ADs and OSDs per Proposal per Facility per version
    • Spot for ATM functionality per version (generation)
  • ATM is all available per facility - no precommitts
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1332
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1563
       
    • Inspect ATM
    • Pressure Plot
      • Jira
        serverDMS JIRA
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
        keySTT-1573
  • Allocation Requests/OS/Blank ATM
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1567
  • another Allocation Version (duplicate)
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1562
  • See PPR Proposal Process Output (Comments/Score)
  • Assign a Preliminary Scheduling Priority per OSD
  • Record comments
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1575
  • Write Narrative per Facility
    • Bare bones, capture comments
  • Create Proposal Summary
    • Bare bones
TAC Meeting
  • Allocation Review Object
    • TAC Comments to PI
      • Jira
        serverDMS JIRA
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
        keySTT-1574
  • UI Prototype (TAC meeting)
    • Spot for Facility Reports
    • List of Proposals/Proposal Summary
      • Proposal metadata (authors/abstract/title/Joint/Thesis/SRP/Triggered/Large/Total Time/Facilities/Trigger criteria)
      • Feasibility Review
      • Proposal Review
        • Scientific Merit Metric
        • Comments to PI
        • Internal Comments
      • Allocation Review
        • Comments to PI (from TAC)
        • Internal Comments (from TAC)
      • Allocation Requests/OSs
      • Allocation Dispositions/OSDs
        • Internal Comments from Scheduler
        • Scheduling Priority
  • Produce Reports for TAC from an Allocation Version
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-1572

Director's Review

  • Directors Report (statistics_:
    • the number of proposals submitted, approved (priority A, B, F), filler (C), rejected (N), and oversubscription (submitted/approved); and by proposal hours: the requested time, the available time, the approved time (priority A, B, F), filler time (C), rejected time (N), and the pressure (requested hours/available hours)

  • csv with

    • ALLOCATION REQUEST ID, PRINCIPAL INVESTIGATOR, NORMALIZED LINEAR-RANK SCORE, REQUESTED TIME, and APPROVED TIME (broken down by semester) for each SCHEDULING PRIORITY (A, B, C [filler], F [fixed], and N [rejected])

  • Approve each OSD
  • Publish the  Allocation Dispositions for Director's Review
  • Approve Allocation Dispositions/ OSDs
  • UI Prototype (Directors Review)
    • Spot for Directors Report
    • List of Proposals/Proposal Summary
      • Proposal metadata (authors/abstract/title/Joint/Thesis/SRP/Triggered/Large/Total Time/Facilities/Trigger criteria)
      • Feasibility Review
      • Proposal Review
        • Scientific Merit Metric
        • Comments to PI
        • Internal Comments
      • Allocation Review
        • Comments to PI (from TAC)
        • Internal Comments (from TAC)
      • Allocation Requests/OSs
      • Recommended Allocation Dispositions/OSDs
        • Internal Comments from Scheduler
        • Scheduling Priority
    • Approve Allocations
    • Update Scheduling Priorities

Update Scheduling Priorities/Approval

  • Produce Directors Reports for Directors Review from an Allocation Version
TTA Member ToolsGenerate MetricsMechanism to track project completion (Need for carryover)  Not in Scope


Create Proposal

...


Capability (General)

DescriptionJIRAImplementedLast WorkingTestedStatus
Scientific Justification

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

<Sprint 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

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

General Allocation Request
<Sprint 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Can Select a Facility

Can add one or more AR

Can delete AR

Can rename

General Capability Requests

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

< Sprint 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

Can Delete

Can Add Multiples

Can Rename

Import Field Sources, Spectral Specs

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

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

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

Sprint 30

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

Zeros import.

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

There are units on the headers at import

Status
subtletrue
colourGrey
colorgreen
titleIgnored

HMS DMS doesn't import 

Units not enforced on widget

Field Source and Spectral Specs

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

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

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

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


< Sprint 30

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 38

Status
subtleTrue
colourBlue
colorgreen
titleprod


Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

 Zeros persist in fields

Entries persists

Status
subtletrue
colourRed
colorgreen
titlebug

Negative Values in Dec DMS entry do not display correctly

Status
subtleTrue
colourGrey
colorgreen
titleIgnore for release

Units on fields

Precision

Status
subtleTrue
colourGrey
colorgreen
titleconfiguration feature

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


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

Status
subtletrue
colourGreen
colorgreen
titleworking

Calibration Parameters

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

Sprint 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

  • VLA
    • Polarization calibration triggers
      • Pol Angle scan
      • Leakage scan
  • GBT
    • Polarization calibration triggers
      • leakage scan
    • Test Source triggers test source scan
    • flux density triggers flux density scan
Performance Parameters

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

Sprint 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

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

Advanced Tab


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

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

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

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

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

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

Sprint 36

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

Filtering Works as expected

Units exist on fields

Angular Resolution is present for VLA

Import Widget has units

Status
subtleTrue
colourRed
colorgreen
titlebug

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


Status
subtleTrue
colourYellow
colorgreen
titleReview

Relationship and hierarchy on Advanced Tab + Performance Parameters

  • Add FS, SS → Advanced tab → upload LAS, RMS for all sources → Performance → specify LAS, RMS, and AS
    • behavior is understood in ticket 992. Need more feedback but behavior acceptable.
Science Target List

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

Sprint 32Sprint 37.3Sprint 37.3

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

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

Simple partitioning, calibration strategy, and capability specific slew time and requested time calculations

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

Sprint 30

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

working but not scientifically checked

Editing Observation Specification

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

< Sprint 30Sprint 37.4Sprint 37.4

Status
subtletrue
colourGreen
colorgreen
titleworking

Can add by target

Can add by Hardware (Simple)

Moving Scans works as expect

General Observation Specification


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

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

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

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

Sprint 32

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colourGreen
colorgreen
titleworking

Times in tabs and summary are reporting consistently

Filtering works

Status
subtleTrue
colourGrey
colorgreen
titleIgnore for release

Precision on entries

Status
subtleTrue
colourRed
colorgreen
titlebug

GBT time calculation uses bandwidth instead of spectral resolution.

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

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtleTrue
colourGreen
colorgreen
titletest

Sprint 39

Status
subtleTrue
colourBlue
colorgreen
titleprod

v0.1.2

Status
subtletrue
colorgreen
titleworking




Version Reports

Expand
titleversion 0.1 report

Landing Page

Updated 10.12.22 for sprint 39, v0.1.2



DescriptionJIRAImplementedLast WorkingTestedStatus
  • Message of the Day on landing page

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


Sprint 34Sprint 37Sprint 37

Status
subtleTrue
colorgreen
titleworking

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


Solicitation Creation



DescriptionJIRAImplementedLast WorkingTestedStatus

Create a Simple Solicitation from JSON for

  • VLA
  • GBT

not implemented/requirements not in a story:

  • modify parameters such as frequency ranges on bands

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

Solicitation Config Files


Sprint 16Sprint 16Sprint 30

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

Configure Field Source, SS, PP, CP





Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

Configure Advance Tab options





Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

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



 

Status
subtleTrue
colourBlue
colorgreen
titlenot implemented
Solicitation Tab

Sprint 37.3Sprint 37.3

Only available to TTA Member



Navigation


DescriptionJIRA/BehaviorImplementedLast WorkingTestedStatus

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

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

<Sprint 29Sprint 37Sprint 37

Status
subtletrue
colourGreen
colorgreen
titleworking

Saving within a CR

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

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

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




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

Status
subtleTrue
colourYellow
colorgreen
titleReview

Saving and AR

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

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




Status
subtleTrue
colourYellow
colorgreen
titleReview

Observation Specification Generation

Popup warns user is overwriting their OS.

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

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

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

<Sprint 35Sprint 37.5Sprint 37.5

Status
subtletrue
colourGreen
colorgreen
titleworking

Navigate and Edit OS on fresh AR



Not Implemented

Status
subtleTrue
colourGrey
colorgreen
titleignored for release

Create Proposal


Capability (General)

DescriptionJIRAImplementedLast WorkingTestedStatus
Scientific Justification

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

<Sprint 32Sprint 37.4Sprint 37.4

Status
subtletrue
colourGreen
colorgreen
titleworking

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

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

General Allocation Request
<Sprint 32Sprint 37.4Sprint 37.4

Modify text or remove entirely

Can Select a Facility

Can add one or more AR

Can delete AR

General Capability Requests

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

< Sprint 32Sprint 37.4Sprint 37.4

Status
subtletrue
colourGreen
colorgreen
titleworking

Can Delete

Can Add Multiples

Import Field Sources, Spectral Specs

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

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

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

Sprint 30Sprint 37.4Sprint 37.4

Status
subtletrue
colourGreen
colorgreen
titleworking

Zeros import.

Widget matches well to headers

There are units on the headers at import

Status
subtletrue
colourGrey
colorgreen
titleIgnored

HMS DMS doesn't import 

Units not enforced on widget

Field Source and Spectral Specs

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

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

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

< Sprint 30Sprint 37Sprint 37

Status
subtletrue
colourGreen
colorgreen
titleworking

 Zeros persist

Negative Numbers work as expected

Status
subtleTrue
colourGrey
colorgreen
titleIgnore for release

Units on fields

Precision


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

Status
subtletrue
colourGreen
colorgreen
titleworking

Calibration Parameters

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

Sprint 32Sprint 37.4Sprint 37.4

Status
subtletrue
colourGreen
colorgreen
titleworking

Performance Parameters

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

Sprint 32Sprint 37.4Sprint 37.4

Status
subtletrue
colourGreen
colorgreen
titleworking

Advanced Tab


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

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

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

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

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

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

Sprint 36Sprint 37.4Sprint 37.5

Status
subtletrue
colourGreen
colorgreen
titleworking

Filtering Works as expected

Units exist on fields

Angular Resolution is present for VLA

Import Widget has units

Status
subtleTrue
colourRed
colorgreen
titlebug

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


Status
subtleTrue
colourYellow
colorgreen
titleReview

Relationship and hierarchy on Advanced Tab + Performance Parameters

  • Add FS, SS → Advanced tab → upload LAS, RMS for all sources → Performance → specify LAS, RMS, and AS
    • behavior is understood in ticket 992. Need more feedback but behavior acceptable.
Science Target List

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

Sprint 32Sprint 37.3Sprint 37.3

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

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

Simple partitioning, calibration strategy, and capability specific slew time and requested time calculations

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

Sprint 30Sprint 37.3Sprint 37.4

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

working but not scientifically checked

Editing Observation Specification

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

< Sprint 30Sprint 37.4Sprint 37.4

Status
subtletrue
colourGreen
colorgreen
titleworking

Can add by target

Can add by Hardware (Simple)

Moving Scans works as expect

General Observation Specification


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

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

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

Sprint 32Sprint 37.5Sprint 37.5

Status
subtletrue
colourGreen
colorgreen
titleworking

Times in tabs and summary are reporting consistently

Filtering works

Status
subtleTrue
colourGrey
colorgreen
titleIgnore for release

Precision on entries

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

Status
subtletrue
colorgreen
titleworking





Misc


Expand
titleHidden For later

Display Precision

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

...