Prioritization Items to Discuss

1. Legacy Requisitions 

   Jira Legacy
   server SSDT JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca key USASR-3370

   1. Previously it was decided to remove Legacy Requisitions from the menu when AP Invoice was rewritten due to the new Vaadin UI ease of use and trainability.  At the SSAC meeting last week the ability to search for accounts and see balance information was brought up when the removal of Legacy Requisitions was discussed.  This feature has not yet been implemented in the Redesign, not had it been mentioned in our prior discussions.
   2. Dave Smith then demoed some development code that would improve the ability to search for accounts.  This lead to a discussion of an account search popup type area, similar to the one in usasweb, that would allow the user to search for accounts and see balance information.  This is viewed as almost a necessity for Requisition users to aid them in selecting the proper accounts.  

      Jira Legacy
      server SSDT JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca key USASR-3613

   3. Reminder: Redesign Requisitions do not require account codes.
2. Reporting levels to implement
   1. Classic reports allow the user to sort and subtotal by various account code dimensions and at certain levels within those dimension.  For example, see screenshots of BUDSUM and REVSUM sort options.
   2. Image RemovedImage Removed
   3. We believe the following list is worth implementing, but would like your feedback:
      1. F1 - 1 digit of function
      2. F2 - 2 digits of function
      3. R1 - 1 digit of receipt
      4. R2 - 2 digits of receipt
      5. O1 - 1 digit of object
      6. S2 - 2 digits of subject
      7. OV - 1 digit of OPU

...

New Issues Created Since

...

2-

...

20-2019