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

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

    • 10
    • 9
    • Hide
      Atlassian Update – 19 November 2018

      Hi everyone,

      Thanks for your interest in this issue. We do understand the need to control the scope of an active sprint and this suggestion is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. 

      For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including the top-voted suggestions:

      We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

      To learn more on how you suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 19 November 2018 Hi everyone, Thanks for your interest in this issue. We do understand the need to control the scope of an active sprint and this suggestion is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.  For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including the top-voted suggestions: Further performance and stability improvements Jira email notifications batching  JRASERVER-1369 Mobile app for Jira Server  JRASERVER-46149 Email notifications template editor available from the UI  JRASERVER-7266 Improved filter and dashboard management by Jira administrators  JRASERVER-15900  and  JRASERVER-41269   Adding the "updated-by" JQL search query  JRASERVER-1973 JQL query for showing issues linked by link type  JRASERVER-25640 Support for 4 byte characters in MySQL connection  JRASERVER-36135 We hope that you appreciate our candid and transparent communication. You can learn more about our  approach to highly voted server suggestions here . To learn more on how you suggestions are reviewed, see our  updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • 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.

      Currently, only user with Edit Permission in the projects able to add issues to sprint.

      However, there are some use case where by projects are interrelated and the other project dependent on other project's issues to be resolved. So, having the ability to nominate an issue to be fix in the next sprint in another project is important in this scenario.

            [JSWSERVER-8964] Specific permission to add an issue to a Sprint (or remove an issue from a Sprint)

            +1

            Hmmm "Review this issue in 12 months time"....10 years laterrrrr.

            C'mon guys!! Controlling the scope of a Sprint is fundamental to Agile process.

            I have my contracted testers and developers adding made up bugs to the sprint so they have work to bill. WTF??

            Mike Hillbilly added a comment - Hmmm "Review this issue in 12 months time"....10 years laterrrrr. C'mon guys!! Controlling the scope of a Sprint is fundamental to Agile process. I have my contracted testers and developers adding made up bugs to the sprint so they have work to bill. WTF??

            +1!!

            Simona Mussi added a comment - +1!!

            Wei Shao added a comment -

            This problem has been plaguing sprint managers for a long time, which will cause confusion and even loss of control over the scope of the sprint. I don't think this is a nice-to-have function.
            Can we consider the value of a requirement from this perspective, rather than just relying on voting?

            Wei Shao added a comment - This problem has been plaguing sprint managers for a long time, which will cause confusion and even loss of control over the scope of the sprint. I don't think this is a nice-to-have function. Can we consider the value of a requirement from this perspective, rather than just relying on voting?

            Gor Greyan added a comment -

            It's a shame they haven't been able to implement this for so many years.

            Gor Greyan added a comment - It's a shame they haven't been able to implement this for so many years.

            Everything that was in your roadmap update on this ticket from 5 years ago is now complete, can we please have this minor but very major change, This request had it's 10 year anniversary 2 months ago

            Steve Letch added a comment - Everything that was in your roadmap update on this ticket from 5 years ago is now complete, can we please have this minor but very major change, This request had it's 10 year anniversary 2 months ago

            MiriamD added a comment -

            +1

            MiriamD added a comment - +1

            +1

            Kevin Schelfer added a comment - +1

            +1

            Alex R. added a comment -

            +1

            Alex R. added a comment - +1

              Unassigned Unassigned
              jalbion Janet Albion (Inactive)
              Votes:
              415 Vote for this issue
              Watchers:
              213 Start watching this issue

                Created:
                Updated: