Versions Compared

Old Version 121

changes.mady.by.user Allison Costa

Saved on

compared with

New Version 122

changes.mady.by.user Allison Costa

Saved on

Key

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

...

DescriptionJIRAImplementedLast WorkingTestedStatus

Notification for a Submitted Proposal

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



Sprint 47SprintSprint 47

Status
subtletrue
colourYellowGreen
colorgreen
titleto testworks

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

Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

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


Notification when Review Configuration is Finalized

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

Sprint 47SprintSprint

Status
subtletrue
colourYellow
colorgreen
titleto test

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

Status
subtleTrue
colourBlue
colorgreen
titlenot implemented

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


Notification when TTA Member changes Conflict State of Reviewer

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

Sprint 47Sprint 47Sprint 47

Status
subtletrue
colourYellow
colorgreen
titleto test

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

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


Notification when Consensus Review is finalized

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




Status
subtletrue
colourYellow
colorgreen
titleto test

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


Notification when all ISRs are finalized for a panel

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





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

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





...

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


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

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

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

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

Sprint 43Sprint 43Sprint 43

Status
subtleTrue
colourBlue
colorgreen
titleWorking

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

Status
subtleTrue
colourYellow
colorgreen
titlenot implemented

  • Hard to tell which proposals have been reviewed.

Status
subtleTrue
colourRed
colorgreen
titleto fix

Score needs to be binary

Version 0.3 Outline

DescriptionJIRAImplementedLast WorkingTestedStatus

Scheduler (during ISRs)

  • Source Conflicts






Scheduler (post Consensus)

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





Mechanism to track project completion (Need for carryover)




Create Proposal

...


Capability (General)

...