AssurancePlatform icon indicating copy to clipboard operation
AssurancePlatform copied to clipboard

[User Story]: Display Parent Element Description in Child Element Interface

Open kallewesterling opened this issue 1 year ago • 8 comments

Role

As an assurance case editor

Desired Feature

I want to view the description of a parent element when I am adding or editing a child element

Benefit

So that I can easily reference the parent's details to ensure that my contributions are consistent and appropriately aligned with the parent's claims and objectives

Acceptance Criteria

GIVEN I am editing an assurance case, AND I am about to add or edit a child element (Strategy, Context, Property Claim, or Evidence), WHEN I initiate the process to add or edit the child element, THEN I should automatically see the description of the corresponding parent element displayed in a clearly visible area of the interface.

GIVEN the parent element's description is displayed, WHEN I read the description while adding or editing a child element, THEN the description should remain visible and legible to assist me in formulating the child element's details.

GIVEN I am using the feature to add or edit child elements, WHEN I navigate through different parent elements, THEN the displayed description should update dynamically to match the currently selected parent element.

Dependencies

  • [x] Frontend implementation to dynamically display the parent description in the child element editing interface.

Technical Notes

  • Implement a non-intrusive but clearly visible section in the side panel, that would display the parent description
  • Consider accessibility standards to ensure that all users, including those with disabilities, can access and benefit from this feature

It could be added above "Create new claim" in the screenshot below:

Screenshot 2024-05-30 at 16 34 52

Definition of Done

  • [X] The feature fulfills all acceptance criteria.
  • [X] The code is reviewed and meets team coding standards.
  • [X] All unit, integration, and end-to-end tests are passed.
  • [X] The feature meets accessibility standards set for the project.
  • [X] The code passes the CI/CD pipeline quality controls (style and linting).
  • [X] The feature is merged into the main branch.
  • [X] The feature is deployed and functional in the QA environment.
  • [X] The feature was demonstrated to the team and accepted by the product owner.

kallewesterling avatar May 30 '24 16:05 kallewesterling