Web client: Editing item information from the item status screen does not automatically update item status display
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.2 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
In the xul client, if you edited an item from the item status list view, after saving changes, upon returning to the item status page, the client added a second line for this item showing the updated information for the copy.
In the web client, we return to the item status screen with no visible change to the previously-scanned item. If a field displaying in the grid was changed, the line continues to show the old value for that field rather than the new one.
I've heard two schools of thought about the old xul client's behavior. Some people didn't like that the client added the second line to the item status list. They thought it was confusing. Others thought it was a good way to see a comparison between the old scan and new scan.
In both schools of thought, users wanted to see the new, updated information after the changes were saved. The web client currently doesn't do so. The only way to see the new information is to scan the barcode again or to click to see the Detail View. Refreshing this screen does not work.
I think it would be good to have a discussion about whether we want a save to add a new line to the grid or if we just want it to update the item with the new values. Maybe a checkbox in the interface that determines the behavior is warranted.
Changed in evergreen: | |
importance: | Undecided → Medium |
Changed in evergreen: | |
milestone: | none → 3.3-rc |
tags: | added: signedoff |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
no longer affects: | evergreen/3.1 |
I see value in both approaches and could also see where there might be circumstances where a user would want the two lines and others where it wouldn't be necessary. I think a checkbox to control the behavior on the screen itself would be a great solution.