Is this instance best for a UAT Process flow?

[Jose Hidalgo]

Hello, our current instance is mainly for our IT Partners to track requirements in the form of stories and defects that arise from UAT. My questions:

1) Is there a Jira instance that can be used for a process that follows:

a) It could be a separate project (away from our IT partner's project) that our Product Owner uses to create requirements and features.

b) Once the PO has complete features in scope to develop, they get "moved" to the IT Partners project, where they action the item. Once complete, they assign it to the "UAT Project" for testing to commence. 

c) Within the separate UAT Project (to be used to create a Test Plan, Test Scripts, and everything UAT), the "assigned" tickets can be added to the proper Test Plan for UAT, and results can be documented.

[Christopher Maxwell · Accepted solution]

Hi @Jose Hidalgo , welcome to the Atlassian Community Forums!

What you're describing, by using separate projects, could be achieved through automations that copy or move issues from project to project. The drawback is the lack of visibility (silos) between the various projects.

Another option might be a single project with a custom board for each user (Product Owner, IT Partners, UAT) - and the custom board would show just the status's the particular user is involved in.

• For Product Owners: Workflow status of "Backlog" or "Ready for Development", JQL filter to show only issues in these statuses:

  Example JQL: project = XYZ AND status in ("Backlog", "Ready for Development")

• For IT Partners: Another board focused on workflow status of "Requirements", "Ready for Review", etc. 

  Example JQL: project = XYZ AND status in ("Requirements", "Ready for Review")

• For UAT: Another board. Status could be "Ready for Testing", "In Testing", etc.

  Example JQL: project = XYZ AND status in ("Ready for Testing", "In Testing")

When possible, it's always ideal to get everyone working together, more closely, rather than more separately. 

[Jose Hidalgo]

@Christopher Maxwell - I genuinely appreciate the reply. Our team is focusing on working together so siloed projects is not optimal. Your input is definitely helpful. Thank you.

[Christopher Maxwell]

@Jose Hidalgo Happy to help. And yes, getting everyone working in same project is ideal - which is where Jira's ability to have different custom boards set up to provide different "views" of the issues within a single project can be helpful.

Also, please post an update whenever you decide what your approach will be and/or how it's progressing: doing so will help us all to learn and grow together.

In addition, if your question is answered for now please mark it as answered ('accept answer' option) - doing so helps classify this ticket as 'answered'.