Done
Details
Assignee
Joseph ReimersJoseph ReimersReporter
Joseph ReimersJoseph ReimersPriority
P3Story Points
1Sprint
NoneDevelopment Team
ThunderjetFix versions
Release
Sunflower (R1 2025)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Joseph Reimers
Joseph ReimersReporter
Joseph Reimers
Joseph ReimersPriority
Story Points
1
Sprint
None
Development Team
Thunderjet
Fix versions
Release
Sunflower (R1 2025)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 4, 2025 at 3:50 PM
Updated March 6, 2025 at 3:24 PM
Resolved March 6, 2025 at 3:24 PM
Sorting tables after new data has been entered creates challenges in trying to keep entries together correctly. In order to prevent data corruption, sorting should occur before any data is entered or changed. Once users enter new data, sorting should be disabled.
Scenarios
Sorting
Given user is on the Batch allocation screen in Finance
AND user has NOT made any changes
When user clicks on the Fund Name or Budget Name headers
Then the table can be sorted by Fund Name or Budget Name
Sorting disabled on edit
Given user is on the batch allocation screen in Finance
When user makes any changes or edits to the table
Then sorting is disabled
Sorting re-enabled when edit undone
Given scenario 2
When user deletes or reverses the change
Then sorting is re-enabled