Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9780

Create a seperate permission / role for creating / starting a sprint

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Hello,

      In the current JIRA Agile plugin you need to be project admin of all the participating projects of a sprint to start the sprint (also to create a new sprint).

      For our organization this isn't suitable; any developer needs to have the permission to create a sprint and/or to start a sprint.
      However, giving every developer the project administrator permission to every project that may participate in a sprint isn't the best solution either; project specific settings may be modified which is something that we want to prevent.

      What I would like to have is a specific permission (that can be assigned) that allows the user to create and/or start a sprint.

      Is this something that can be realized?
      It's something that is giving us headaches for quite some time now

      Kind regards,
      Koen Werdler, EsperantoXL

          Form Name

            [JSWSERVER-9780] Create a seperate permission / role for creating / starting a sprint

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3068338 ] New: JAC Suggestion Workflow 3 [ 3662050 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2624540 ] New: JAC Suggestion Workflow [ 3068338 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2326435 ] New: Confluence Workflow - Public Facing v4 [ 2624540 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2043228 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2326435 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2031335 ] New: JIRA PM Feature Request Workflow v2 [ 2043228 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736144 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2031335 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: pre-triaged New: affects-server pre-triaged
            Hoang Dong (Inactive) made changes -
            Component/s Original: Security [ 20091 ]
            Martin (Inactive) made changes -
            Business Value Original: Enhanced [ 10502 ]
            Workflow Original: GreenHopper Kanban Workflow v2 [ 555002 ] New: JIRA PM Feature Request Workflow v2 [ 736144 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Comment [ Many thanks for reporting this issue. Realistically, we are not planning on addressing it in the next 12 months.
            Regards,
            JIRA Agile Team ]

              Unassigned Unassigned
              33c28ea1-6135-4a04-adeb-69425fecc67c Deleted Account (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: