-
Bug
-
Resolution: Obsolete
-
Low (View bug fix roadmap)
-
None
-
6.3.0.2
-
Standalone, JDK 6, RHEL 6.4
-
6.03
-
Creating a sprint requires to have administer project on all projects that have issues in the board's backlog.
Unfortunately, this requirement also includes epics.
This limits users to only filtering by epics in their projects. If their stories belong to epics from other projects, they have to chose between being able to use the epics panel or being able to create sprints.
- relates to
-
-
- Gathering Impact
-
-
JSWSERVER-5035 As a JIRA/GH administrator, I would like to be able to specify who is allowed to create and start a sprint independently from the "Administer Projects" JIRA permission
- Closed
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-9769] Cross project epics prevent from creating sprints
The behaviour in this area has changed since the introduction of sprint permissions, and this ticket is not relevant anymore.
To learn more about the sprint permissions, please visit this link: http://blogs.atlassian.com/2016/02/jira-software-sprint-permissions/
Regards,
JIRA Agile Team
We are forced to add Epics from other (cross-team) project into our board filter to be able to see Epic Names on sprint issues – see related JSW-13790 issue.
However, this requires additional permission in these new affected projects with Epics.
I'm linking the JSW-13790 issue. See also comment there.