Copy Lovell Staging Review tickets to va.gov-team repo

[shiragoodman]

User Story

As a Governance team member, I want to copy all of the Lovell SR tickets to the va.gov-team repo so that those tickets can be reflected in the Collaboration Cycle dashboard in Domo.

Assignee: @CherylEvans
Peer Reviewer: @briandeconinck

Description

Governance team decided to duplicate the Lovell VAMC Staging Review accessibility issue tickets into the va.gov-team repo opposed to having the tickets (currently in the CMS repo) pulled into the Collab Cycle dashboard. The purpose of this ticket is to create the new tickets with the right labels and assign them as child tickets to the Lovell VAMC Collaboration Cycle request ticket.

Impacted Artifacts

all accessibility issue tickets from the Lovell VAMC Staging Review

Tasks

• Create new tickets for each CMS-repo accessibility issue that was flagged at the Lovell VAMC SR
• Ensure the labels added to the new tickets are aligned with the Anatomy of a Staging Review Issue ticket
  guidance
• Comment on the CMS repo issues that this ticket was recreated in the va.gov-team repo and the va.gov-team repo ticket should be closed when the CMS-repo ticket is closed. (Maybe write standard message that can be copy/pasted?)

Peer Review

To be completed by peer reviewer

• User story and acceptance criteria are met

Acceptance Criteria

• The Lovell SR accessibility issue tickets exist in the va.gov-team repo

How to prepare this issue

Refinement

• Ticket has user story, description, tasks, and acceptance criteria
• Ticket has additional appropriate labels, if applicable
• Ticket has been sized
• Once all above items are checked, add the 'Ready' label.

Planning

If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly

• Ticket has been discussed as a team at Planning
• Ticket has been assigned to appropriate initiative or quarterly epic
• Ticket has been assigned to a Sprint
• Ticket has been moved to the Planned pipeline in the Governance team board
• Ticket as an assignee and peer reviewer

[shiragoodman]

Cheryl added as assignee, Brian added as Peer reviewer

[CherylEvans]

@shiragoodman @briandeconinck The Lovell SR ticket, 52672, has only one Accessibility ticket (54290) associated with it, or am I missing something? I expected to see more.

[briandeconinck]

Do you have time after refinement to chat? I can talk you through the whole sordid story.

[CherylEvans]

@briandeconinck Absolutely! :-) Chat soon!

[shiragoodman]

thank you for coordinating!

[CherylEvans]

@briandeconinck This is a WIP. I'll update as I create the tickets. :-)
Update. I recreated all tickets in the va.gov-team repository; the links are below. I will review and refine them individually and add the correct labels. The last thing I'll do is add the note on each ticket (original and recreated) referencing the opposing ticket. I'll reach out if I can't determine the Experience Standard or the appropriate title for the recreated ticket.

CMS ticket: 11364 -> VA.gov-team ticket: 64437
CMS ticket: 11700 -> VA.gov-team ticket: 64449
CMS ticket: 11848 -> VA.gov-team ticket: 64835
CMS ticket: 12070 -> VA.gov-team ticket: 64836
CMS ticket: 12079 -> VA.gov-team ticket: 64837
CMS ticket: 12080 -> VA.gov-team ticket: 64420
CMS ticket: 12082 -> VA.gov-team ticket: 64839
CMS ticket: 12084 -> VA.gov-team ticket: 64840
CMS ticket: 12087 -> VA.gov-team ticket: 64841
CMS ticket: 12088 -> VA.gov-team ticket: 64842
CMS ticket: 12089 -> VA.gov-team ticket: 64843
CMS ticket: 12085 -> VA.gov-team ticket: 64844
CMS ticket: 12063 -> VA.gov-team ticket: 64846
CMS ticket: 12081 -> VA.gov-team ticket: 64847
CMS ticket: 12717 -> VA.gov-team ticket: 64848
CMS ticket: 12068 -> VA.gov-team ticket: 64849
CMS ticket: 12107 -> VA.gov-team ticket: 64850
CMS ticket: 12023 -> VA.gov-team ticket: 64851

[CherylEvans]

@shiragoodman @briandeconinck This ticket will carry over into the next sprint.

[CherylEvans]

@briandeconinck I think this is ready for your Accessibility expertise. Everything is done for these tickets except refining the accessibility language for the titles (We didn't copy over the body, so the title is the only thing needing refinement.) on the va.gov-team repo tickets. I would have been guessing which experience standard was the most appropriate. The labels should all be correct, but you may want to add a few more once you decide on the refined accessibility language for the titles.
I also added a comment on each ticket (original and recreated) referencing the opposing ticket and linked the appropriate tickets.
Please let me know if you have any questions or concerns. :-)

[shiragoodman]

@CherylEvans @briandeconinck one last thing - tickets that are closed in the CMS repo should also be marked as closed in the va.gov team repo. please verify! thank you

[CherylEvans]

@shiragoodman @briandeconinck

Closed Tickets in the va.gov-team repo:

• 64449

• 64844

• 64846

• 64848

• 64849

• 64851

Open tickets in va.gov-team repo

• 64847 Linked to broader ticket # 13804
• 64850 Linked to broader ticket # 12326

[CherylEvans]

@briandeconinck I am ready for your peer review if you are done with your updates. :-)

[briandeconinck]

@CherylEvans I have checked the last of the tickets, I think this is good to go!

[CherylEvans]

@briandeconinck Thank you so much for finishing this up! :-)
Closing.