Versions Compared

Key

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

...

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
bug hunting and final feature push
Sprint 61
bug hunting; final official sprint of versions
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

...

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 47Sprint 4860Sprint 4860

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 47Sprint 60Sprint 60

Status
subtletrue
colourYellowGreen
colorgreen
titleto testWorking

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

Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

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


Notification when TTA Member changes Conflict State of Reviewer

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

Sprint 47Sprint 48Sprint 48

Status
subtletrue
colourGreen
colorgreen
titleWorking

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

Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

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

Status
subtleTrue
colourYellow
colorgreen
titleReview

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

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


Notification when all ISRs are finalized for a panel

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

Sprint 50


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

  • When a reviewer certifies conflicts, all of the proposals that do not have at least
3
  • 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 50Sprint 60Sprint 60

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

Solicitation Creation

...

DescriptionJIRAImplementedLast WorkingTestedStatus

Create a Simple Solicitation from JSON for

  • VLA
  • GBT

not implemented/requirements not in a story:

  • modify parameters such as frequency ranges on bands

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

Solicitation Config Files


Sprint 16Sprint 16Sprint 30

Status
subtleTrue
colourGrey
colorgreen
titlehack for release

Configure Field Source, SS, PP, CP





Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

Configure Advance Tab options





Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

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




Status
subtleTrue
colourBlue
colorgreen
titlenot implemented
Solicitation Tab

Sprint 37.3Sprint 37.3

Only available to TTA Member

A Proposal Prefix can be specified per solicitation

 

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

Sprint 40Sprint 40Sprint 40

Status
subtleTrue
colourBlue
colorgreen
titleWorking

Review Configuration



Status
subtleTruetrue
colourYellowGreen
colorgreen
titleTesting

Review Configuration Tab is with Solicitation creation now

Working

Create a Test Solicitation+Test Proposals
Sprint 46


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

Close Solicitation

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

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

...

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


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

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

Sprint 44SprintSprint 48


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.There is a save 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.




...

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 persistSave
  • Feasibility groups (back burner)
  • Assign independent science review to a member of a different SRP
  • Upload and use a configuration file
  • Filtering on Panels/proposalsShould not be able to assign the same person to multiple panels
  • Can delete reviewers


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

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


Status
subtleTrue
colourYellow
colorgreen
titleNot implemented

  • feasibility groups on placeholder

Status
subtleTrue
colourRed
colorgreen
titleto fix

  • Should be able to select multiple chairs (currently can only do one)
  • Drop down menu on available Science Categories should either be linked to Solicitations or the drop down menu on the available science categories on the vetting should be linked to the master list.
  • Should not be able to assign the same person to multiple panels.
  • Delete reviewers



Finalize Review Configuration

  • Finalize can occur when
    • all proposals are vetted
    • the Solicitation is Closed
  • Pop-up asking 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

Sprint 45Sprint 59Sprint 59

Status
subtleTrue
colourBlue
colorgreen
titleWorking

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

Status
subtleTrue
colourYellow
colorgreen
titlereview

  • 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

...