[UXPROD-4601] Support versioning of Lists Created: 17/Dec/23  Updated: 05/Jan/24

Status: In Progress
Project: UX Product
Components: None
Affects versions: None
Fix versions: Quesnelia (R1 2024)

Type: New Feature Priority: P3
Reporter: Kathleen Moore Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by FAT-10223 Create Karate tests for mod-lists ver... Closed
is defined by MODLISTS-57 Refactor list deletion so that we can... Closed
is defined by MODLISTS-61 To store updated lists in the list_ve... Closed
is defined by MODLISTS-62 Create individual list version reques... Closed
is defined by MODLISTS-63 Include list_versioning in refresh data Closed
is defined by MODLISTS-72 Create main /lists/{id}/versions endp... Closed
is defined by MODLISTS-75 Historical versions are saved with in... Closed
is defined by MODLISTS-76 Enhance getListVersion(s) APIs to inc... Closed
is defined by MODLISTS-42 Spike: Refactor list deletion so that... Closed
is defined by MODLISTS-53 Spike: Add versioning of lists Closed
is defined by MODLISTS-60 Create list_versions table Closed
is defined by UILISTS-96 Include list_versioning in refresh data Draft
is defined by UILISTS-50 Poll on the list landing page to upda... Blocked
Relates
relates to MODLISTS-74 Unable to delete lists with new versi... Closed
Release: Quesnelia (R1 2024)
Development Team: Corsair
PO Rank: 0
RCA Group: TBD

 Description   

Current situation or problem: Tracking list deletion, along with generally being able to track changes, is an enabler to make other features possible (e.g., undo, change auditing, soft delete, debugging, etc). This initial work will be scoped to enable polling for deleted lists in order to provide UI notifications for list deletions.

In scope

  • Tracking all previous versions of a given list
  • Providing limited list details for a previous version of a list
  • Tracking the previous version(s) of a list when a list is modified in the following ways:
    • changing the list name
    • changing the list description
    • changing the FQL query
    • changing the user friendly query
    • active/inactive
    • private/shared
    • deleting the list
  • Only the following tracked information will be available for previous versions of list:
    • version number
    • list name
    • list description
    • FQL query
    • the user friendly query
    • active/inactive status
    • private/shared visibility
    • is the list deleted

Out of scope

  • Tracking the record set for a given version of a list
  • Tracking the previous version(s) of a list when a list is modified in the following ways:
    • refreshing a list (the record set)
    • changing the visible columns
  • Being able to revert to a previous version of a list

Use case(s)

Proposed solution/stories

Notes:

  • how/if we track visible columns is still TBD ** 

Questions

 


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