Unable To Complete Sprint Due To Filter Query

[Cameron Beaulieu]

Hi all, I know there are some similar posts around this question, but I can't find anything that matches this issue in particular.

I'm having the issue where based on the Board Filter Query I am unable to Complete my current sprint or start a new one (the buttons don't show up). I isolated which part of the query is causing this issue and have found that it is the portion where it says "parent = ACTRL-484", where I am trying to pull in tickets that belong to a certain epic (I don't want the rest of the tickets from that project).

What is strange is when I change the filter to the following, I am able to complete the sprint (the button shows up). This pulls in the all the tickets from that given project rather than just the subset that have the parent I listed.

I've checked the permissions and on each of the projects and I have the proper permissions to Manage Sprints (I have all permissions in all the projects that I am pulling from). I have also tried changing how I pull in those tickets by using "Epic Link" instead, as well as "assignee" (one person is working on all of them), but both of these queries result in the same issue.

So that's the issue, any suggestions would be greatly appreciated!

[Fernando Eugênio da Silva]

Hey @Cameron Beaulieu , Welcome to the Atlassian Community!

Considering a board that contains multiple projects, you really need to have 'Manage Sprints' permission on all of these projects.

Apparently the problem is in the query (Parent = ACTRL-484). If CTRL-484 is an Epic or another issue at a higher level, it can be a Parent of any other issue within your Jira site.

I would tell you to look at all the issues that are within this Parent ACTRL-484 to validate that within them and in each of your projects you also have Manage Sprints permission (including the ACTRL project itself).

You need to have Manage Sprints permission on all projects that contain issues displayed in their filter result. Once you do this review, you should be able to manage your prints with your filter.

[Cameron Beaulieu]

Hi @Fernando Eugênio da Silva, thanks for the response and the welcome!

As I mentioned above, I have checked that I do have the 'Manage Sprint' permission on all the projects.

Checking what exists within the Epic is a good point, but everything exists within the ACTRL-484 Epic are ACTRL stories. 

Since when I pull in the full project into the board, I am able to complete the sprint, I'd say it is unlikely to be a permission issues (if it was a permission issue for Manage Sprints for the ACTRL project, I would be unable to Complete Sprint when anything from that project is part of the filter query).

If you have any other suggestions, please let me know!

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

I think there is a big clue in "Since when I pull in the full project into the board, I am able to complete the sprint".

That suggests to me that your board filter or mapping are not including all the issues that are in the sprint (it might be both), but to close a sprint.  To close a sprint, all issues, including sub-tasks must be shown on the board (does not matter where they are shown, they can be in any column on the board).  My guess is that someone has changed your board filter, and/or the column status mappings after starting the sprint.

[Cameron Beaulieu]

@Nic Brough -Adaptavist- I've checked and the ACTRL parent portion of the query pulls in a total of 3 tickets. I've confirmed that all three of these appear on the board as expected. Should I be checking anything else to confirm if that is the issue? Below I've attached image 1, which ACTRL tickets appear from the filter query, and image 2, which ACTRL tickets appear on the board (under the In Progress column)

I also might be missing something, but if I pull in the full project and can complete the sprint, wouldn't that imply that if I pull in a subset of the tickets (like from a certain Epic), I should also be able to complete the sprint? If those 3 tickets are causing the issue, they would also get pulled in with the rest of the ACTRL project, so wouldn't I expect the same behaviour of not being able to close the sprint?

Any suggestions on what to check would be great. Apologies if I am missing something or misunderstanding your comment.

[Nic Brough -Adaptavist-]

Yes, parent = x is probably returning issues that are not on the board.

I would want to

• compare the whole board filter with the parent=x filter to see what the differences are
• Run a search for just "sprint = x", naming the sprint you are trying to close,
• Given those two, look at why the issues it returns are not on the board

[Cameron Beaulieu]

Thank you for the help @Nic Brough -Adaptavist- it did take a while, but your suggestion to go through those queries ticket by ticket to cross compare helped. Ended up being someone had created an incorrectly assigned task that was not included in the board, exactly as you had suggestion.

Again, thank you for all the help, definitely learned something new from this!

[Nic Brough -Adaptavist-]

Missing issues from boards is always a horrid one to debug when it's not you who did it!