Prioritization Issues to Discuss

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

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

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

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

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

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

7. Would you like the create new/save option available on customers like is currently available on ledger codes.  

   When importing billings from the grid, should we be creating ledger codes that do not exist? The regular import does a get-or-create on the ledger code, there is no separate import. 

   1. Add an option to create missing ledger codes and default to true?

   2. Do we always want to create the ledger codes or should this be optional?  Or always create them when they don’t exist?  If they choose NO then you’ll receive an error if a ledger code doesn’t exist. 

8. Do you want to be able to edit the billing number?
   1. Downside - if you’ve sent the bill out to the customer; there will be a disconnect between the bill and the customer.
   2. Benefit - the billing number can be corrected if needed.
   3. Would you prefer billing and payment numbers be auto assigned, meaning you can not manually enter the billing or payment numbers at all?  Like Classic, wouldn't be able to change, must delete and re-post.
      1. If an error with the billing number is made (numbers transposed and gap created): If the bill is already sent to user, district will have to update in transaction configuration to set new high number to fill in the gap.
9. Billing service date, should this default to a specific date if the user does not populate it?
10. Billing grid default sort is by due date and then billing number, is this the desired default sort?

All Issues Created Since 25 Feb 2020 

...