-
Suggestion
-
Resolution: Tracked Elsewhere
-
None
-
None
-
None
When a user edit an issue to be part of an issue, it's pretty possible that, if he/she has two different sprints with the same name (for example "Sprint 1"), one on each project and the customer closes the issue, the user may have no permission to close that issue at the other project.
So my suggestion is that the Sprint have the name of the project that it's running at the "Sprint custom field.
- is related to
-
JSWSERVER-6850 Moving issue from project in rapid board to another project results in inability to close or start sprint for non admin
-
- Closed
-
- relates to
-
JSP-210945 You do not have permission to view this issue
Form Name |
---|
Sprints are not related to projects, they are are related to issues and can be related to the board in which they were originally created. They can appear in any board where the issue is included in the filter that the board is based upon.
The issue around closing a sprint with issues from different projects where a user may not have the permissions for all projects is tracked elsewhere, please see https://jira.atlassian.com/browse/GHS-6850