Is it possible to have workflow statuses before and after the scrum sprint?

Sorry if this is a basic question - I'm pretty new to using JIRA in depth.

 

Basically we have approval processes before our items go into sprint. And once the sprint is complete, we have a release process working with a third party. So for example, once the scrum items are 'done', we have another stage - 'pending release' and then 'released'.

Is it possible to be able to close the sprint, have items counted as closed (as the dev team have done everything) but then have another status afterwards.

Would really appreciate any help.

3 answers

1 votes

Yes, but you won't be able to represent it on the scrum board.

You can easily set up a workflow such as

New -> Accepted for dev -> in progress -> Done -> Deployment

And then run the Scrum based only on Accepted/in progress/done.  You either change the scrum board filter to exclude new and deployment, or do not use them in the board columns.  When you're setting this up, the important thing to remember is that Scrum considers the far right hand column as "done", and nothing else.  That's why you'd want to leave "deployment" off the board.

You can have another board (Kanban probably) that covers all the status so you can still visualise it all and move cards to deployment or out of new.

Thomas Schlegel Community Champion Oct 25, 2017

@Nic Brough [Adaptavist] - I have to type faster :-)

1 votes
Thomas Schlegel Community Champion Oct 25, 2017

Hi Zuber,

welcome to Atlassian Community. Don't apologize for asking basic questions, everyone of was new to Jira sometimes.

But back to your question (which isn't basic at all in my opinion).

Yes, you can create scrum boards based on part of your workflow. You have to set the board's filter query, so that it only shows the issues that belong to the status' you want to see in the board. Assign all these status to the matching columns. An issue is considered "done" in the context of the board, if it has reached the most right column of the board.

You have to take care that your issues don't get off of the board by changing the status to something that is not covered by your filter query. 

You can also have more than one board for your project. E.g. another board for testing your issues. That board may start then with the next status after development is ready. Or you work with your issues without another board.  

  

Nic, Thomas, - thank you so much for such a swift and thorough response. Glad to see such a great community on here. This helps me loads :)

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,782 views 11 18
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot