-
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
-
JSWSERVER-13790 Epic Name is not displayed on issue row on Backlog view
-
- 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
[JSWSERVER-9769] Cross project epics prevent from creating sprints
Minimum Version | New: 6.03 |
Workflow | Original: JAC Bug Workflow v2 [ 2855081 ] | New: JAC Bug Workflow v3 [ 2937572 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542077 ] | New: JAC Bug Workflow v2 [ 2855081 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550545 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542077 ] |
Remote Link | New: This issue links to "Atlassian KB - Users with the permission to administer projects in a sprint are still unable to start a sprint (Web Link)" [ 330243 ] |
Link | New: This issue relates to JSWSERVER-13790 [ JSWSERVER-13790 ] |
Labels | Original: triaged | New: affects-server triaged |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 909890 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550545 ] |
Resolution | New: Obsolete [ 11 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
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.