Title Description Acceptance Criteria Area Path

Transcription

1 Q2 1 1 Ability to track UOCAVA in the Voter Record Voters flagged UOCAVA should have an UOCAVA (Military or Overseas) s to UOCAVA should be tracked in the Voter Audits. Online Processing: UOCAVA_STATUS = A should populate as Military UOCAVA_STATUS = C should populate as Overseas UOCAVA should be available in Voter Search. (Military, Overseas, Both, None) 3/27/ :08 AM Q2 1 2 Remove Obsolete UOCAVA-Related Absentee s The following absentee types should no longer be available for new requests. Military Military Overseas Military Dependent Overseas Resident Overseas Non-Resident Existing active upcoming requests of these types associated to active voters should be updated with a new absentee type. If the request is flagged PMIV the new type should be Permanent Mail-In, otherwise it should be Date Range. \System Configuration 12/17/ :58 PM Q2 2 3 Three New Absentee Request Issue Methods There should be new issue methods avialable in Absentee Request: FWAB (Only available for Election Specific requests) Address Locator Ballot (Only available for Election Specific requests) Online Transmission (Available for all absentee types) 1/29/2013 1:21 PM Q2 3 4 Add a New ABS Request Application Source called Emergency Ballot Application "Emergency Ballot Application" should be available as an Application Source in Absentee Details. This should only be available for Election Specific requests. 3/27/ :45 AM Q2 1 5 Voter - No Default Transaction Transaction should not default to Voter Initiated. User must select either Voter Initiated or Administrative before saving any changes to a voter record. There should be keyboard shortcuts for selecting Voter Initiated or selecting Administrative. When a user selects a batch to be processed, the system should ask the user if it is Voter Initiated or Administrative. While processing the batch the Transaction should be selected by the system and should not be available for user to modify. If the user closes the batch and reopens the batch for processing they will be asked again. When validating a batch the system should select Administrative and user should not be able to change it. 1/29/2013 3:03 PM

2 Q2 1 6 Remove/Map/Hide Multiple VR Transaction Sources The following transaction sources should be removed: All other agencies (existing references should be mapped to Agency Serving Persons with Disabilities) Admnistrative Action (existing references should be mapped to Mail-In ) Any other source not listed (existing references should be mapped to Mail-In ) Returned Ballot (existing references should be mapped to Mail-In ) Absentee Application (existing references should be mapped to Mail-In ) Human Services (existing references should be mapped to NVRA Agencies) Election Day - Misc/Other (existing references should be mapped to Election Day ) Branch Moter Vehicle Offices (existing references should be mapped to Department of Revenue) Election Signature Card (existing references should be mapped to Election Day ) Mail/Mail-In Ballot Affidavit Signature (existing references should be mapped to Mail-In ) 3/27/ :12 AM Q2 1 7 Pre-s 3/27/ :15 AM

3 Q2 1 8 Make "Issue Method" Attached to the Ballot The Absentee Request has an "Issue Method" field. But, this is not always the actual way a ballot (with Issue Sequence 1, 2, or 3) is issued. Sometimes a Replacement Ballot needs to be faxed instead of the originally requested Mail method. SCORE currently only tracks Issue Method based on the Absentee Request. In Election Management -> Print Absentee Labels -> Print button -> Add a new, required field called "Issue Method". This new drop down would list all Issue Methods available in SCORE. This would allow the user to assign a specific Issue Method for that specific ballot, regardless of what the Absentee Request showed. The ballot's assigned Issue Method would be captured system-wide and shown in places like Active Ballots, the Ballot Audit Log, the Election Log and Reports & Labels. In Election Management -> Print Absentee Labels -> Reprint button -> Add a new, optional field called "Issue Method". When entered, prompt user that it will update all ballots in that batch; similar to when the user modifies the Sent Date. This new drop down would list all Issue Methods available in SCORE. This would allow the user to assign a specific Issue Method for that specific ballot, regardless of what the Absentee Request showed. The ballot's assigned Issue Method would be captured systemwide and shown in places like Active Ballots, the Ballot Audit Log, the Election Log and Reports & Labels. In Voter -> Issue Ballot -> Add a new, required field called "Issue Method". This new drop down would list all Issue Methods available in SCORE. When user Reprints a label, the Sent Method should not be modified. This would allow the user to assign a specific Issue Method for that specific ballot, regardless of what the Absentee Request (if there is one) showed. The ballot's assigned Issue Method would be captured system-wide and shown in places like Active Ballots, the Ballot Audit Log, the Election Log and Reports & Labels. Development Considerations: How this works for a Mail Ballot Election when there may or may not be an Absentee Request. In Early Voting -> Carry Button, it brings up the Issue Ballot screen. The Issue Method drop down should be auto-filled with Over the Counter and not modifiable. Note: This ticket replaces WIN-341. When printing/reprinting a ballot label through Voter >> Issue Ballot screen, users should have the ability to specify the issue method of the ballot. Appropriate ballot audits should be posted for any change in issue method. The system should be updated to use the issue method of the ballot instead of the issue method of the absentee request Q2 1 9 Untitled \ 11/30/ :53 AM 3/27/ :17 AM Q Schedule Jobs Export/Report - Parameter Metafile A metafile should be created when exporting data from SCORE. The metafile should contain the parameters the user selected when running/scheduling the report. \Schedule Jobs 4/1/2013 1:44 PM

4 Q CDOS Comments as of 09/26/12 - CDOS Ticket for either 2013 Q1 or 2013 Q2. Functionality of Voiding an Absentee Request During Inactivation of the Record Removing a voter from active status should remove an active absentee request even there is not a ballot. Situation presented to Trent from Shawna in Jefferson County for voter ID : Voter record was in Denver County and was issued a Mail Ballot. Ballot was voided and record moved to Jefferson County. Record was saved active. Later, record was made Inactive - Returned Mail (with an Effective Date that was after the Denver Municipal Election cutoff date, but before the Election Day). PMIV request was kept "active" instead of becoming "voided". Enhancement Request: When the above situation occurs, the "active" absentee request should be made "void". Note: Currently only PMIV requests are made void when the record becomes Inactive (to remove them from the PMIV list per statute). System does not void Election Specific Requests when moving to another county or made Inactive - they simply are no longer eligible for that ballot. 9/26/ :20 AM Q "Add Non Duplicate Issue 1: Voter" search screen Voter module -> "Add Non Duplicate Voter" should search for voters of all Status and fixes Status Reasons. It currently does not display at least the Cancelled records. The user should have ability to Add Non Duplicate Voter to any record, regardless of status/status reason statewide/countywide. Fix requested by Debbie in Montrose, Shawna in Jefferson, Stephanie in Teller, and pretty much every other county statewide. Issue 2: Voter module -> "Add Non Duplicate Voter" does not allow user the keyboard shortcut keys for CTRL+V to paste informaiton into the following cells. Search screen should allow the use of CTRL+V. General tab -> Voter ID field Residential Address -> Zip field Mailing Address -> Zip field Mailing Address -> Zip4 field Fix requested by Shawna in Jefferson and Disa in Arapahoe (now in Douglas). 1/28/2013 3:41 PM

5 Q Discrepancies between Voter Records Appearing on VR-005 and Appearing in Voter Merge Module Issue: Kit Carson and Park Counties have found discrepancies between VR-005 and the Voter Merge module. Kit Carson County found three people on their VR-005, but in the Voter Merge module (groups identified by the system), only two appear on the screen. After reviewing the records, nothing has been modified in the records according to the Audit Log and the user. See attachments. Park County has found two examples where their VR-005 is showing one record in the group and the VR-005 module is showing two records in the group. Obviously there should be at least two records identified on the VR-005. See attachments. The VR-005 and Voter Merge's Groups Identified by the System should be the same and correct. Merge Bug 3/7/ :27 AM Q Access Ticket created on 04/02/2012. Enhancement: Add "Multiple Active, Inactive, Incomplete, or Pending Groups Only" checkbox to VR-005 Search Screen CDOS created Custom Extract CE-025 to take the current VR-005 run statewide, and break it into only groupings that have only two or more of the following Statuses: Active, Inactive, Incomplete, Pending. This means that a group with only one of those statuses, and the rest of the records are Cancelled, can be manually put into a spreadsheet for counties to review. If SCORE had a search parameter on the VR- 005 Potential Duplicate Voters Report, then this CE-025 would not be needed. The actual name of this checkbox may need to be approved by CDOS. Enhancement Request: Add a search parameter on the VR-005 screen to only show groupings that have two or more of the following Statuses: Active, Inactive, Incomplete, and/or Pending. The Report and Export would still export the same correct information, in the same format, but would only show groupings where there were two or more records with Active, Inactive, Incomplete, and/or Pending statuses. The group may or may not contain Cancelled records. \Reports and Labels 4/2/2012 4:12 PM

6 Q New Voter Status and Status Reason: Not Registered - Failed 20 Day Period Due to CDOS Policy, need a new status and status reason in SCORE. This would replace the current "Cancelled" status with "F2D: Failed - 20 day period" status reason. New Voter Status Code: "R" Description: "Not Registered" This would be shown in System Configuration and available throughout the system (like in Voter module). New Voter Status Reason Status: "Not Registered" Code: "FTD" Reason: "Failed 20 Day Period" This would be shown in System Configuration and available throughout the system (like in Voter module). Statewide, the current records marked as "Cancelled" as "Failed - 20 day period" should be changed to "Not Registered" as "Failed 20 Day Period". This would be an administrative change and the appropriate audit log entries should be posted with the User Name as "System" (this is how we did it when adding the State Date statewide). The current "Cancelled" as "Failed - 20 day period" status reason should then be removed system-wide. 2/5/2013 9:36 AM Q Spirit Ticket Created Date: November 16, Voter : Tab Order Attached in Excel document is the desired Tab Order (when user hits Tab on the keyboard) and Reverse Tab Order (Shift Tab on the keyboard) for the Voter Module as of 04/03/13. There are two tabs in document, one is the main Voter Screen, and the other is the FWA Link. In Spirit, this ticket was linked to SCORE Virginia in Larimer and Disa in Douglas have both requested the tab order be updated. 10/3/2011 9:29 AM Q Users Should Not Be Able to Scan Images into Non Survivor Records Issue: Currently in Voter module, users have the ability to type in a non survivor voter ID, pull up the record, and click the scan button. The system lets the user scan in a document and select the Document Template. Users don't realize they are scanning into a non survivor. Users should not be able to scan images into non survivor records in SCORE. The scan button on the voter registration image area should be disabled (grayed out) if the record is part of a merge (non survivor record). 3/28/ :57 PM

7 Q Voter Search's Clear button needs to remove No Abs Request checkbox selection Issue: Voter Search -> Select Absentee tab -> Check "No Abs Request" checkbox -> Conduct search -> Clear search. Notice the screen flashes, as if everything is cleared, but if you click on Absentee tab, screen still has "No Abs Request" selected. Issue found during testing of WIN-661 in 2012 Q3/Q4 UAT testing. When Clear button is used (via keyboard or mouse), the "No Abs Request" should be removed automatically. Search Bug 3/20/2013 9:28 AM