Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,297,138
Community Members
 
Community Events
165
Community Groups

Jira workflow separation

We have an big issue where we start a sprint and our "done" is UAT then its up to the business to when they get around to testing issues. However its been 8 months and i have yet to complete and release a sprint and there is not one report that clearly defines how well we did because most issues stay in UAT or ready for prod and some in waiting for information from business and this goes on for some time. So how can we work a workflow to benefit us and either separate uat and ready for prod within one sprint if possible. Is there any help when issues like this come to play. How can I have a better workflow knowing there is just going to be a issues that will not move and when they do it will be at different times so they cannot be timed within the sprint. I would like the reports to show case how much we do and for us getting it into UAT is our Done. So how can reports show case that and not include UAT or ready for prod and waiting etc ????  Thank you any help would be greatly appreciated. 

2 answers

2 accepted

0 votes
Answer accepted

Hi @Esmeralda DeArmas

There is infinite ways to go about this. And currently I always recommend that process steps outside of the team's workflow should be managed in their own ticket. 

As you mention UAT is your done, one solution could be:

1. In your own project, cut UAT and everything that comes after it, replace UAT by done.
2. Create a project dedicated for the business team that needs to validate and instruct them to manage their tasks there. 
3. Set up a Jira Automation rule that automatically creates a ticket in the business team's project, linked to your ticket. 

You'll now be able to actually close stuff at the end of your sprint and you'll be able to report better lead times on your own tickets. 

KR,
Wouter

0 votes
Answer accepted
Mikael Sandberg Community Leader May 16, 2022

You should reconfigure your board and the filter that it is using. Once an issue hits the right far most column it is considered done and will show up in reports as such. If you leave out UAT and ready for prod from the filter you you should then be able to close sprints normally.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,648 views 37 46
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you