Redline Box and Mark as Single Object

[m-prodan]

• As an IAO User
• I want to be able to delete my redaction in a single action
• so that I don't have to duplicate my efforts when removing redactions.

Assumptions & Scope This story is from our prioritization and feedback sessions with IAO Super Users.

Users found it difficult to remove redactions, this is because the annotation and the mark for the redline are drawn as two separate objects. This also clutters the redaction/annotation panel, as every redline will include two objects - the box itself, and the annotation.

To address this - we believe the annotation should be embedded into the redline object itself - this could be achieved by creating the annotation as a 'reply' to the redline/mark for redaction as that contains everything to a single object.

What is IN scope? Creating redlines using the box/selection tool Creating redlines for full page redactions Creating redlines for the find and redact feature from the redaction panel

What is NOT in scope?

Acceptance Criteria

Scenario 1: Mark for Redaction - box/selection tool

• GIVEN a user is on the document reviewer
• WHEN they draw a box for redaction
• OR use the select text for redaction feature
• AND they select an appropriate FOIPPA section(s)
• THEN the selection will have a red box
• AND will be annotated with the section(s) number as a reply to the redaction mark

Scenario 2: Mark for Redaction - Full Page

• GIVEN a user is on the redact by page feature
• AND they have selected page(S)
• WHEN they click on mark for redaction
• AND they select an appropriate FOIPPA section(s)
• THEN the selected pages will be marked for full redaction
• AND will be annotated with the section(s) number as a reply to the redaction mark

Scenario 3: Mark for Redaction - Find and Redact

• GIVEN a user has completed a search on the redaction panel
• AND they have selected object(s)
• WHEN they click on mark for redaction (or redline)
• AND they select an appropriate FOIPPA section(s)
• THEN the selected objects will be marked for redaction
• AND will be annotated with the section(s) number as a reply to the redaction mark

Scenario 4: Deleting Redaction Box

• GIVEN a user has selected a redlined box in the document reviewer
• WHEN they delete the redlined box
• THEN the redlined box and annotation/section number will also be deleted

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)

Validation Rules? (If yes, list here)

Design @xxx - please link the Design here

Definition of Ready

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

Definition of Done

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

[m-prodan]

Assumption - there is no need for me to write a bug ticket around being able to delete a redaction box and annotation in a single click. This user story should eliminate that bug. Thoughts welcome @lmullane @liseandtea @KyEggleston

[KyEggleston]

It's a 'one or the other', so makes sense