Prioritization Items to Discuss

1. Jira Legacy
   server SSDT System JIRA serverId 925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca key USPSR-3959

    What is the correct filter criteria to use to eliminate old compensations from selection lists?

2. Jira Legacy
   server SSDT JIRA serverId 925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca key USPSR-3961

    This was reported as a high priority item for a district moving to USPS-R. Since a payroll can be immediately un-posted with little to no risk the question is how high should we prioritize this?

3. Jira Legacy
   server SSDT JIRA serverId 925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca key USPSR-3990

    In 2019 Pennsylvania will be requiring electronic submission of W2 information. It is likely they adhere to the SSA format and we will attempt to implement this in a manor that will work for any state that uses the SSA submission format. The question is if specific coding is required to support each state what are the critical states that must be supported? Indiana, Pennsylvania, Michigan, West Virginia, others?

4. Jira Legacy
   server SSDT JIRA serverId 925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca key USPSR-3869

    Was released on 5.21.0 and will now validate direct deposit pay distributions at payroll post. The question was raised via feedback as to whether we should validate the pay distribution completely at the time is is saved (created). We tend to default to validating things at the last responsible moment in order to facilitate date entry. For instance if you wanted to start setting up an employee's pay distribution but did not have their account number on hand. The question is is the convenience allowed by this worth not validating the pay distribution on save if it will be validated on payroll post?

   columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6d21ed14-3f48-3cc2-ad28-6548879d10d6 key USASR-3370

All New Issues Created Since 11-20-2018

...