Collaboration Cycle Staging Review issue tickets are included within the dataset that populates the Collaboration Cycle Dashboard on Domo.

Sample issue ticket

Sample Collaboration Cycle GitHub ticket showing general formatting and Issue specific details.

Title

An example issue title, Markup and meta data - HTML markup isn't valid - 09.01.1.

The title of the page is made up of 3 fields:

[VA.gov Experience Standard Category Name] VA.gov Experience Standard Issue Name (Unique ID)

The Unique ID uses the following syntax:

(XX.YY.Z)

Where

XX = VA.gov Experience Standard Category Number

YY = VA.gov Experience Standard Issue Number

Z = Instance Number

The Unique ID is only unique within the context of the specific VFS product Staging Review. The Unique ID can be repeated when viewing all VFS teams and/or all VFS products.

Body

General information of issue ticket containing VFS team name, VFS product name, and Point of Contact and Reviewers.

VFS team name

The owner of the VFS product being reviewed in the Staging Review.

VFS product name

The name of the product or feature being reviewed in the Staging Review.

Point of Contact/Reviewers

The name of the Platform reviewer who uncovered the issue. This is who the VFS team should contact if there are questions and/or concerns about the issue. There may be more than 1 name listed.

Issue details of ticket containing issue details, steps to recreate, VA.gov Experience Standard reference, and Other References such as WCAG.

Platform Issue

The VA.gov Experience Standard Issue name. This is the same field that is populated in the title of the ticket.

Issue Details

The feedback from the Point of Contact/Reviewer specific to the issue found. If more than 1 person is listed as Point of Contact/Reviewer, Issue Details will be provided from all individuals.

Link, screenshot or steps to recreate

The reference information from the Point of Contact/Reviewer. This could be in the form of a link to the staging review page where the issue was found, a screenshot of the issue in the staging environment, or steps to recreate the issue in the staging environment. This field may or may not be populated.

VA.gov Experience Standard

This is the VA.gov Experience Standard Category number and the VA.gov Experience Standard Issue number. This always links to the VA.gov Experience Standards page on Platform Website. The category number and issue number should match the numbers listed in the ticket title.

Platform recommendations and VFS team tasks to complete for issue ticket.

Platform Recommendation

The recommended action from the Point of Contact/Reviewer in order to fix, resolve and/or mitigate the issue.

VFS Team Tasks to Complete

Instructions to the VFS team on how to contact Platform with any questions/concerns, and how and when to close out the ticket. This is auto-populated in every Staging Review issue ticket.

Labels

Labels that are added to issue ticket including team label, product label, practice area labels, and CCIssue number.

Default labels

Staging Review issue tickets will have all of the labels listed below:

  • collab-cycle-feedback This label indicates that the issue ticket is feedback from a Collaboration Cycle reviewer.

  • CC-Dashboard This label indicates that the issue ticket will be included in the dataset for populating the Collaboration Cycle Dashboard in Domo.

Practice Area labels

Staging Review issue tickets will have at minimum one at maximum four of the labels listed below:

  • 508/Accessibility This label indicates that the issue impacts the accessibility practice area.

  • design This label indicates that the issue impacts the design practice area.

  • content This label in indicates that the issue impacts the content practice area.

  • ia This label indicates that the issue impacts the IA practice area.

Collaboration Cycle touchpoint labels

Staging Review issue tickets will have the staging label listed below:

  • staging This label indicates that the ticket was documented during the Staging Review.

  • midpoint This label indicates that the ticket was documented during the Midpoint Review.*

  • design-intent This indicates that the ticket was documented during the Design Intent.*

*At this time, the midpoint and design-intent labels are not in use.

Severity labels

Staging Review issue tickets will have at minimum zero at maximum one of the labels listed below:

  • launch-blocking This label indicates that the issue detailed in the ticket is launch blocking and must be resolved before the team is permitted to launch in production.

VA.gov product labels

Staging Review issue tickets will have exactly one product label. Please refer to VA.gov Product Directory for a complete list of VA.gov product labels.

VFS team labels

Staging Review issue tickets will have at minimum one team label. Please refer to the VFS Teams tab of the VFS Team Roster for a complete list of VFS team labels.

VA.gov Experience Standards labels

Staging Review issue tickets will have exactly one of the labels listed below:

As of 10/22/2021, there 90 Issues total across 12 categories, including Category 00 Issue 00. This is subject to change. Please be sure to reference the VA.gov Experience Standards page for the complete and up to date list of issues.

Accessibility labels

Staging Review issue tickets will have at minimum zero at maximum one of the labels listed below:

  • 508-defect-0 This label indicates that the issue is an accessibility defect level 0. If this label is on the ticket, the launch-blocking Severity label must also be applied.

  • 508-defect-1 This label indicates that the issue is an accessibility defect level 1. If this label is on the ticket, the launch-blocking Severity label must also be applied.

  • 508-defect-2 This label indicates that the issue is an accessibility defect level 2. If this label is on the ticket, the launch-blocking Severity label may also be applied and is at the discretion of the Accessibility practice area reviewer.

  • 508-defect-3 This label indicates that the issue is an accessibility defect level 3.

  • 508-defect-4 This label indicates that the issue is an accessibility defect level 4.

Please reference the Accessibility defect severity rubric for additional information on the accessibility labels.

Additional labels

Staging Review issue tickets may include additional labels for VFS team reference (eg the product label, status labels, VFS role labels, etc.) or for Platform reference (eg accessibility subject matter, etc.).

Epics

Epics section of GitHub and parent ticket (if any).

Collaboration Cycle moved to a new process beginning May 2022.

  • For those who started the Collaboration Cycle process prior to May 2022, Staging Review issue tickets must be child tickets to the Staging Review epic.

  • For those who started the Collaboration Cycle process during/after May 2022, Staging Review issue tickets must be child tickets to the Collaboration Cycle GitHub ticket

VFS teams are free to assign the Staging Review issue tickets to other epics.