Issue detail view- editing the sprint - only the sprints of the issues project should show

[Sven Koch]

I refer to issue detail view and pressing the edit button to assign / change a sprint

When editing an issue only the sprint of the issues project is in should show up.

However, all sprints from all projects on the server show up which is error prone (assigning to the wrong sprint) and makes no sense.

And if I could paste a screenshot you could even see the visual proof of the problem

Therefore:
Is there a way to change the configuration so only the project specific sprints show up?

JIRA server 7.4.x

[Andy Heinzer · Accepted solution]

Hi Sven,

If I understand your concern here it is that when you are editing an issue in Jira, changing the sprint field of an issue allows you to set any existing sprint name.   This is actually by design.

The reason for this is actually based in the fact that sprints are not bound to any single project or board.   You can have issues from multiple projects exist in the same sprint.  You can also have the same sprint appear in multiple boards spanning across multiple projects.   Because of this fact, there is no mechanism in Jira Software currently to restrict the values that appear for that field directly.

There is an existing feature request for this in https://jira.atlassian.com/browse/JSWSERVER-10805 I would recommend watching and voting on this issue if this is something you would like to see. 

However rather than trying to change the value of that field directly on issues, I think it might be better method to instead create a new board.  This new board could be based of a custom JQL filter, a filter that includes only the issues/projects that exist in the sprints that you want to change the issues' sprint membership between.  This way you could simply drag and drop the issues on the board between different sprints.

The other thing to watch out for here is sprints with the same names.  If you have more than one sprint with the same name, it becomes very difficult to know that you are selecting the correct sprint when you are directly editing the sprint field on the issue itself.  Whereas when using the board to change which issues exist in which sprint, it tends to be a bit easier to prevent accidentally placing the issue into the wrong sprint.

[Sven Koch]

Hi Andrew,

thanks for the clarification that sprints can span over projects and that this is therefore by design.

This fact was not clear to me yet

[Peter Chester]

Ok, so we have multiple customers who should NOT be able to see sprints or projects for other customers. This is a security concern. 

We've locked down permissions on sprints so that people only see the sprints that they should see. However, when looking at the issue detail view in a board, if you click the sprint to change it, you see ALL sprints across the company regardless of permissioning. This seems to me to be a bug with permissioning and a pretty nasty one at that.

I totally get that it's designed to let you select cross project sprints if you want. But what about those of us (i suspect most users) who actually don't want to see sprints across projects and have gone out of the way in permissions as such?