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; } } }

Sprints from different projects close simultaneously

BenWade

There is already a similar discussion of this problem, however, no proper answer.

I have 2 projects A and B. I create sprints in the backlog of these projects. I name sprints differently to not accidentally assign issue to the wrong project's sprint. I name them this way A-Sprint 1 and B-Sprint 1.

I decided to check if I accidentally assigned issues to the wrong project's sprint. for this I go to issues>go to all issues>filter by project A> +More >Sprint> B-Sprint and I repeat these steps one more time for project B>A-sprint. I do not know if it is the correct way to verify, but I am doing this way. So no issues were assigned incorrectly.

Whenever I close the sprint e.g. B-Sprint it closes the A-sprint as well although I renamed the sprints. It also shows that 1 issue cannot be closed and there are open subtasks. however, there are no open subtasks. It drives me crazy, how to tackle this problem? any help?

Please provide step by step solution if possible.

some stories/tasks have linked issues from the different project. Can this cause this issue?

Accepted answers

Trudy P Claspill

Hello @BenWade

Can you provide screen from these two boards showing that they have two differently named sprints?

To find out if you have issues assigned to the wrong sprint you need to not include the project in your search.

I decided to check if I accidentally assigned issues to the wrong project's sprint. for this I go to issues>go to all issues>filter by project A> +More >Sprint> B-Sprint

If you constrain the filter by project that can obscure what issues are actually in the sprint.

Do a search based only on the sprint and see what the results are.

All comments

Rudy Holtkamp

Hi @BenWade ,

First of all projects don't have backlog, but Scrum boards do. There is a subtle but very important difference between a project and a board. A board is a visual representation of a filter which can include multiple projects.

And that is where things probably go wrong for you. Both boards are not mutually exclusive. Could you post the board filters below, we might figure out a way to make them mutually exclusive.

Kind regards,

Rudy

BenWade

filter list
Only the last two filters assigned to projects. unassigned filters cant cause this problem right?

Filter 1

project = "BI Projects" and sprint in openSprints()

Filter 2

project = "Commercial Excellence" and sprint in openSprints()

Filter 3

project = COMEX ORDER BY Rank ASC

Filter 4

project = BI AND issuetype in (standardIssueTypes(), subTaskIssueTypes(), Bug, Epic, Story, Task, Feature, "Sub task") ORDER BY Rank ASC

BenWade

I can delete these filters if it helps me to solve the problem. This problem drives me crazy. I have around 300 issues and I have a mess now.

Rudy Holtkamp

First thing I noticed in filter 4

project = BI AND issuetype in (standardIssueTypes(), subTaskIssueTypes(), Bug, Epic, Story, Task, Feature, "Sub task") ORDER BY Rank ASC

You want all standard issues types, subtask issue types and epics in you filter. I think you can suffice with 'project = BI ORDER BY Rank ASC'

For filters 1 & 2 why is the clause 'and sprint in openSprints()' added? Could you explain the relevance? Or are only filters 3 & 4 your board filters?

Because only the board filters are relevant (the location is: board > board settings > general > filter query)

Rudy Holtkamp

the sprint contains:
-1 completed issue
12 open issues

I currently have a total of 11 issues, so it's giving the incorrect count. I suspect the problem lies somewhere in this area.

You mention '11 issues' are these stories/tasks/bugs (= level 0 hierarchy issues) or do they include subtasks?

It's very hard to see what is the problem. It might be that you are completely right and that there is a indexing problem. I suggest you contact Atlassian support, so they can dive into this.

BenWade

@Nic Brough -Adaptavist- @Trudy P Claspill Guys, may I ask your help help with this problem. What else can casue this problem?

Trudy P Claspill

Hello @BenWade

Can you provide screen from these two boards showing that they have two differently named sprints?

To find out if you have issues assigned to the wrong sprint you need to not include the project in your search.

I decided to check if I accidentally assigned issues to the wrong project's sprint. for this I go to issues>go to all issues>filter by project A> +More >Sprint> B-Sprint

If you constrain the filter by project that can obscure what issues are actually in the sprint.

Do a search based only on the sprint and see what the results are.

BenWade

Now I got, there were 1 wrongly assigned Epic. Epic from Project B was in the sprint of project A.
thank you for your help 🙌. I will close the current sprint on the 2nd of October. I will accept your answer if closing one sprint won't close the other. Will let you know if this issue still persists or not.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud