Tracking issue after sprint for deployment

Hi,

We have a sprint development cycle of ToDo, Developing, Testing and Done. When the issue is done it is marked as resolved and ready for deployment.

I would like to get some ideas on how people manage the deployment process in Jira Agile. At the moment I have the following situation:

- A sprint can contain issues that will be deployed in different releases.

- We have a process of Resolved(ToDo), Testing server, Production server(Done/Closed)

Regards,

Tim

3 answers

1 accepted

Hi Benito,

This is correct.

I created a workflow ToDo -> Developing -> Testing -> Resolved -> Testing server -> Production server(Closed) but I have the following problem:

Sprint (ToDo -> Developing -> Testing -> Resolved)

Kanban (Resolved -> Testing server -> Production server(Closed))

The sprint and kanban share the same "Resolved" status. This is causing trouble if the issue is moved from "resolved" to "testing server" before the sprint is completed. The issue is then not included in the sprint result and story points are not included.

Is there an option of triggering a new status for "resolved" issues when an sprint is marked as completed?

Regards,

Tim


Hi Tim! The 'triggering' of course would only work, if deployment takes place AFTER the sprint completion. The question remains what to do, if a workflow with the need for timely deployments is in effect. Any suggestions on that anyone?

0 vote

Hello Tim!

If I understood you correctly, you are using the scrum to create your backlog and plan your sprint, and then throw the sprint onto the kanban board to manage it's execution.
If I got it right, I'd say this is very good way to handle things, since you can use the quick (kinda non-stop) execution of kanban while doing the whole control of the bigger picture on scrum.

Cheers!

Benito Picarelli

0 vote

Hello Tim!

If I understood you correctly, you are using the scrum to create your backlog and plan your sprint, and then throw the sprint onto the kanban board to manage it's execution.
If I got it right, I'd say this is very good way to handle things, since you can use the quick (kinda non-stop) execution of kanban while doing the whole control of the bigger picture on scrum.

Cheers!

Benito Picarelli

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published 4 hours ago in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

26 views 0 3
Read article

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