Hello, Dear CNV leads.
As part of our VME department, Goals were presented today on the all hands. Specifically, the "Alignment" and "Overload reduction" Goals,
we are planning to align CNV Jira project to Fit the Project definitions that are used in all other VME Products (MTA, MTV, MTC, OADP) and Workflows that are used in Openshift.
Most of the changes will be transparent for you and automatic.

Below is the list of planned changes. Please review and reply if you have any concerns.

1. CNV Issue Type Schema will be changed from
OJA-ITS-018 (Outcome, Feature, Feature Request, Epic, Story, Bug, Task, Weakness, Vulnerability, Sub-Task) to
OJA-ITS-020 (Feature Request, Epic, Bug, Story, Task, Closed Loop, Vulnerability, Weakness, Sub-Task) - As already planned, All the "Features" in CNV project will be moved to the Parent VIRTSTRAT project and owned by PMs.
A new type " Closed Loop" will be added to CNV Jira to help to improve Customer experience. (QE folks are aware of this process, and we will explain it in detail later)

2. CNV will move to the Workflow Schema of Stories/Taks/Subtasks that is used in Other VME projects and OCP from OJA-WF-AD C to OJA-WF-BA
OJA-WF-AD New, Backlog, To Do, In Progress, Review, Stakeholder Acceptance, Release Pending, Closed

OJA-WF-BA: New ➔ Planning ➔ To Do ➔ In Progress ➔ Dev Complete ➔ Testing ➔ Release Pending ➔ Closed
Epic, Feature Request will use simple OJA-WF-J: Epic, FR - New, Refinement, In Progress, Closed

We have the changes already implemented in Stage if you would like to review:
https://issues.stage.redhat.com/secure/Dashboard.jspa?selectPageId=12365726

The changes will also allow us to use ClosedLoop type for better Customer escalations and experience, to track program-level Features in VirtStart, together with MTV and OADP and UX features.
As well as better present our Work with Worktypes and where do we spend our time.