nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

we have 3 different tasks for 1 problem statement with the same Task number in jira software

Durga Solse

for example -

for the Npa Recovery problem task no is - 123, we have 3 tasks

1 for the BA team - the BA team will create a user story on the same task no within BA Project and the same

second developer task, the developer change status according to their development phase

and third one Tester, the tester changes their task status according to their Testing Phase

So in these cases when we try to close the Current Sprint, we get Different status

and the Sprint is not Closed.

For the closing sprint, we required the same Task status

so how we can maintain these Processes for closing Active Sprint?

Accepted answers

Trudy Claspill

Hello @Durga Solse

Can you provide screen images that show us these tasks?

Are they subtasks under a parent issue?

Are they tasks in one project or different projects?

Durga Solse

@Trudy P Claspill As you can see in the below Image -

I've listed the Task Information for Various Projects here.

Therefore, the Active Sprint cannot be closed every time I try to do so because we have a different status with subtasks.

Screenshot from 2023-04-20 11-07-53.png

All comments

Trudy Claspill

Hello @Durga Solse

Can you provide screen images that show us these tasks?

Are they subtasks under a parent issue?

Are they tasks in one project or different projects?

Durga Solse

@Trudy P Claspill

they are subtask under a parent issue

and they belonging different Project

Trudy Claspill

Issue that are Subtasks cannot be in a different project than their parent issue. Can you please provide a screen image that shows these subtasks within their parent task? Please show the issue key for the parent and subtasks. You can black out other information that is confidential.

When trying to close a sprint only the issues in the column farthest to the right will be considered complete. For any issue that has subtasks, those subtasks must also be in the column farthest to the right. If there are subtasks in the other columns, the parent issue of those subtasks will not be considered complete. Jira will prompt you to choose between moving the incomplete issues to the backlog or another sprint.

Can you explain what you are trying to accomplish that does not line up with that functionality?

Durga Solse

@Trudy P Claspill As you can see in the below Image -

I've listed the Task Information for Various Projects here.

Therefore, the Active Sprint cannot be closed every time I try to do so because we have a different status with subtasks.

Screenshot from 2023-04-20 11-07-53.png

Trudy Claspill

Technically you can close the Active sprint, but it will move the "main task" to the next sprint (or backlog) because that task will not be considered "complete".

For the main task to be considered "complete", the status it is in and the statuses that its subtasks are in must be statuses that are in the right-most column of your sprint board. Looking at your image, if the Development Complete status is the the only status in the right most column, then main task 9599 and the subtasks 9600 and 9601 must also be in the Development Complete status. Then the main task will be considered complete.

The status of the Linked Issues (AB-1216) does not have any impact on whether or not the main task is considered complete when you try to close the sprint.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud