Loading...

Type: Suggestion
Resolution: Fixed
Component/s: None
Labels:

Current Status:

Hide

Atlassian Status as at 22 February 2016

This feature is now available for both JIRA Software Cloud and JIRA Software Server.
The server release version is 7.1.0, please see the server release notes for further details.

Previously we had discussed the intention to consolidate the add or remove an issue from sprint into the Manage Sprints permission. However, we have determined that this will not be a workable solution for many of you. More details in comment #872704 below.

Kind regards,
Martin
JIRA Software

Show
Atlassian Status as at 22 February 2016 This feature is now available for both JIRA Software Cloud and JIRA Software Server. The server release version is 7.1.0, please see the server release notes for further details. Previously we had discussed the intention to consolidate the add or remove an issue from sprint into the Manage Sprints permission. However, we have determined that this will not be a workable solution for many of you. More details in comment #872704 below. Kind regards, Martin JIRA Software
Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

NOTE: This suggestion is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding suggestion.

At the moment, creating and starting a sprint (from the Rapid Board) is based on the "Administer Projects" permission. This does not make much sense for us, as the JIRA/GreenHopper administration is not done by the Scrum team themselves, but they need to be able to manage their sprints on their own.

Therefore, we need to specify which users/groups/project roles are allowed to start a sprint independently from the "Administer Projects" permission.
To be honest, the reliance of GreenHopper on JIRA permission feels often inadequate and I hope that you find a way to manage GreenHopper permissions independently (this relates to ~~GHS-1787~~, GHS-3928).
As long as this is not possible, maybe there is a way to at least separate starting a sprint from the "Administer Projects" permission? E.g. by adding a "Manage Projects" permission in JIRA that allows some of the things included in the "Administer Projects" permission?

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

GHS-5035.jpg
105 kB
02/Dec/2014 4:06 PM
Jira_-_Permissions_and_Airmail.jpg
52 kB
12/Aug/2014 5:55 AM
JIRA Agile Most Voted.jpg
484 kB
02/Dec/2014 1:28 PM

details

JSWCLOUD-6754 As an Atlassian (enterprise) customer I request that Rapid Board fulfills some MUST HAVE requirements

Closed

duplicates

JSWCLOUD-4701 Allow non project admin users to release from Rapid Board

Closed

incorporates

JSWCLOUD-6850 Moving issue from project in rapid board to another project results in inability to close or start sprint for non admin

Closed

JSWCLOUD-11751 Improve Permissions Error Messages for Sprint Management

Closed

is duplicated by

JSWCLOUD-4701 Allow non project admin users to release from Rapid Board

Closed

JSWCLOUD-7285 As an user, I would like to be able to Release a Sprint without being a Project Administrator

Closed

JSWCLOUD-7851 Allow user to start a sprint even though the user is not administrator of all projects with issues in the sprint.

Closed

JSWCLOUD-9780 Create a seperate permission / role for creating / starting a sprint

Closed

JSWCLOUD-10158 finer permissions for putting Issues into sprints

Closed

JSWCLOUD-10867 Start and stop a sprint

Closed

JSWCLOUD-11615 JIRA shouldn't require Project Administrator permissions for starting/closing sprints

Closed

JSWCLOUD-12078 Create Sprint and Sprint planning should not be tied to the Project Admin Permission

Closed

JSWCLOUD-13520 Sprint/Scrum Master Needs Full Admin Access to Project

Closed

is related to

JSWCLOUD-6850 Moving issue from project in rapid board to another project results in inability to close or start sprint for non admin

Closed

JSWCLOUD-6388 Restrict 'Remove Issue from Sprint' operation to users with Schedule permission / Administer Projects permission

Closed

JSWCLOUD-6986 Why is creation of Sprints restricted based on project level admin permissions?

Closed

JSWCLOUD-7881 As an admin of the board, I'd like to have users with "Schedule Issues" permission to be able to add or remove an issue from/to a sprint

Closed

JSWCLOUD-8845 Ability to define permission to create status via Simplified Workflow

Closed

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

JSWCLOUD-3928 As a GH administrator, I would like the ability to define which groups have the ability to rank issues across project

Gathering Interest

JSWCLOUD-8964 Specific permission to add an issue to a Sprint (or remove an issue from a Sprint)

Gathering Interest

JSWCLOUD-13265 Provide UI method to identify origin board for a sprint

Gathering Interest

relates to

JSWCLOUD-6388 Restrict 'Remove Issue from Sprint' operation to users with Schedule permission / Administer Projects permission

Closed

JSWCLOUD-12577 Big improvements possible

Closed

JSWCLOUD-13025 Having a separate permission for Active sprint and Planned sprint

Closed

JSWCLOUD-5977 As a Scrum Master (using Rapid Board) I would like to restrict users who can add/remove tickets from sprint

Gathering Interest

Testing discovered

JSWCLOUD-13053 Granular Project Permissions for creating/ordering sprints

Closed

(8 is duplicated by, 9 is related to, 4 relates to, 1 Testing discovered)

Details

Description

Attachments

Attachments

Issue Links

Forms

Activity

People

Dates