paulsonder
commented
3 months ago @jamlung-ri I'm bouncing this back to you so we can organise a session on requirements.
We have an initial design, so an hour over a Miro board should ensure we can round out on the needs and add to the dev queue.
Background and context
Briefly describe the background or context of this user story. Include relevant links to documents or diagrams created in the planning phase, or dependencies.
For any concept in OCL, there are often multiple versions that represent the state of the concept at different times. When names, descriptions, custom attributes, etc. are added, removed, or changed, a new concept version is made. These versions come together as a single historical record, which can be seen in this Concept History section.
Currently, a gap is that it only recognizes concept changes (e.g. new name, description, custom attribute), but not the changes to a concept's mappings.
Smart Checksums are likely going to come in handy to make this History section more powerful, and it hopefully should address the mapping changes too as described above.
User Story
As a: Dictionary manager I want: to view changes that have occurred to a concept over time, plus when they happened (perhaps along with who made the change?) So that: I can identify changes to a concept and determine if that change has happened since I last checked in, made a collection using that concept, etc.
Design: UX / UI documentation
Attach links to Zeplin documentation
Dependencies
Identify any dependencies or related tickets that must be completed before or alongside this task and link them in Zenhub.
Technical Requirements
Acceptance Criteria
Testing Criteria
Outline specific testing criteria or scenarios to ensure the feature meets the user story requirements.
Notes, comments and assumptions
Additional notes or comments for clarification, including potential risks or uncertainties.