Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira tickets in closed sprint moved from QA to in progress get stuck in old sprint.

John Fisher
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 29, 2018

Hi I just noticed a couple of tickets had been put into QA, the sprint had then been closed. The tickets then got put back into "In progress" by testers but the tickets get lost and devs didn't notice as they were in the old closed sprint still.

Not sure if this is a workflow issue or not - Is there is a way for tickets in old sprints  and they are put back to Development to get automatically moved into active an sprint so that the Developers will see them?

1 answer

1 accepted

1 vote
Answer accepted
Chris Nicosia
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 31, 2018

@John Fisher If they were in the last column of the board when the sprint was closed and subsequently reopened after the sprint was closed, they should have returned to the backlog as an open ticket. 

From a technical perspective, I'm sure there is a way to accomplish this,  with a workflow plugin like Jira Misc Workflow Extensions or Scriptrunner when the ticket is transitioned back to "In progress" and automatically add it to the current sprint but the logic may be a little complex to find the right active sprint value.  

It may be simpler to do one or more of the following:

  • Train users to watch for these Jira notifications when these tickets are reopened.
  • Setup a filter subscription or a dashboard widget to monitor when this situation occurs (tickets recently reopened that were in a completed sprint but not in the current active sprint
  • Examine the reopen transition with the team to determine the scenarios when it is used and if it is transitioning the ticket to the correct status and assignee.
John Fisher
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 31, 2018

@Chris Nicosia Thanks for the response!

 

You are right the simplest way of dealing with this is train the devs to watch for the notifications. This is always going to be a bit of a problem though as I know that the Dev's seem to miss the notifications quite a lot, especially when they are busy.

I think I will get testers to message the dev who is assigned to ticket whenever it doesn't pass QA. This way they will be getting 3 notifications, email, their slack work-log channel and a DM. 

Suggest an answer

Log in or Sign up to answer