Ordering functionality that FOLIO needs to stay competitive (UXPROD-3440)

[UXPROD-204] Display a history of edits for a record that is being viewed in acquisitions Created: 20/Jan/18  Updated: 06/Dec/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: Sunflower (R3 2024)
Parent: Ordering functionality that FOLIO needs to stay competitive

Type: New Feature Priority: P3
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Unresolved Votes: 0
Labels: LC-priority1, SolutionArchitecture, acq-morningglory-candidate, acquisitions, loc, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UXPROD-3215 Display a history of edits for the Or... Closed
is defined by UXPROD-4111 Organizations - Display a history of ... Closed
is defined by UXPROD-3456 Invoice - Display a history of edits ... Draft
is defined by UXPROD-3457 Organizations - Display a history of ... Draft
Relates
relates to UXPROD-1141 Create, close, cancel, Purchase Orders Closed
relates to UXPROD-910 Change Tracker Open
Release: Sunflower (R3 2024)
Epic Link: Ordering functionality that FOLIO needs to stay competitive
Front End Estimate: Large < 10 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: XL < 15 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Thunderjet
Kiwi Planning Points (DO NOT CHANGE): 1
PO Rank: 131
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R4
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

Current situation or problem: Not enough metadata is captured regarding record activity. Some records (eg. order) are edited frequently and often by different users. currently it is only possible to see who last edited the order and who created it. This could make it really difficult to trouble orders over time and uncover why something has not been for filled or what the implication are of cancelling it etc.

NOTE this feature is being split for implementation and prioritization so it does not have estimates

 

  • Orders UXPROD-3215
  • Invoice UXPROD-3456 
  • Organizations UXPROD-3457

Links to additional info

Analysis continuing in wiki at https://folio-org.atlassian.net/wiki/x/agVU

Questions



 Comments   
Comment by Dennis Bridges [ 03/Mar/20 ]

This issue is moving to Q3 as it may be a larger platform issue that requires discussion with stripes force. Relates to UXPROD-910 Open

Comment by Khalilah Gambrell [ 14/May/23 ]

Dennis Bridges  - is this a duplicate feature? 

Comment by Dennis Bridges [ 08/Sep/23 ]

This is a general feature that covers multiple acquisitions record types. Features have now been created to represent work that needs to be done for each record type. Once completed this will be closed. As such it has been converted to an Umbrella assigned to a later release.

Generated at Fri Feb 09 00:06:31 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.