Forums

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

How to close a sprint where all issues are ready from Sprint scope of view, but not yet Resolved

Patrik Grönvall October 8, 2020

Dear community,

We have a workflow for defects which can in short be described as

Analysis -> Development -> Acceptance Test -> Resolved.

 

The development team are working using JIRA sprints, but their responsibility ends when development (and module testing) is done, where the defect is handed over to the Acceptance Test Team, to be tested once the release is shipped (once every 3-4 sprints or so).

Now to the problem. The Development team can not close the sprint in JIRA properly, as the JIRA Defect issue is completed from their point of view, but it is not yet Resolved in JIRA, as it has to pass all the states in the Acceptance test phase of the workflow.

Do you know of a suitable way around this? Today they move these issues into the next sprint, although all the work needed by the development team is already done.

Kind regards

Patrik Grönvall, ITM Tools Service Manager, DB Schenker, Sweden.

1 answer

1 accepted

0 votes
Answer accepted
P_D_ Foerster
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.
October 8, 2020

Hi Patrik,
I recommend adding another status like Development done or Pending acceptance test. Then configure only Analysis, Development, and your new status on the Scrum board of your development team in the corresponding columns. The new status must be mapped to the right most column (green color = done) on your Scrum board. Issues that are placed there are treated as done when you complete a sprint.

For your acceptance test team use a separate board (scrum or kanban as you like) and map the new status to the left most column on that board.
This way issues that have moved to let's say Development done now have the reference to the completed sprint and immediately appear on the acceptance test team board.

Caveat: should members of the acceptance test team transition an issue from Development done to Acceptance test, then the issue would disappear from the dev team's board before your dev team could complete the sprint. This would lead to inconsistencies since not all issues would get the reference completed sprint.
To workaround this put all remaining workflow statuses in the right most column of the dev team's board an be sure to move the card to the proper action / status when putting an issue in the right most column.

Hope that helps!

Patrik Grönvall October 8, 2020

Solved the problem with input from another issue I read here. But reading your input it was excatly the same solution.

It was so that all the status in the workflow from the end of the Development Phase "Ready for Delivery" were not put in the last column of the Scrum Board in JIRA.

Once I adjusted that everything works as we want it to.

Thanks for your input.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.7.1
TAGS
AUG Leaders

Atlassian Community Events