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

As a user I would like to add an issue to a sprint from the Issue Navigation Dialog

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 6.3.9
    • None
    • 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.

      Coming from a dedicated customer:

      It is quite in efficient and time consuming to add issues to sprints in progress: You have to open the rapid board, go to plan mode, search up the issue, drag and drop from backlog to sprint. With an operation available through hot key or the operations dialog on the issue navigation page one could easily add task to a sprint. If you want to make it really elegant one could by default add to ongoing sprint with the option of adding it to upcomming sprint

      In case the issue can be a part of many Rapid Boards, there could be a way to select from a list.

            [JSWSERVER-6303] As a user I would like to add an issue to a sprint from the Issue Navigation Dialog

            We are pleased to announce that this issue has now been resolved in JIRA Agile version 6.3.9 which is now available to download.
            https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.3.9+Release+Notes

            Thank-you for your feedback and votes on this issue.
            Kind regards
            Martin
            JIRA Agile team

            Martin (Inactive) added a comment - We are pleased to announce that this issue has now been resolved in JIRA Agile version 6.3.9 which is now available to download. https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.3.9+Release+Notes Thank-you for your feedback and votes on this issue. Kind regards Martin JIRA Agile team

            This is very important for our Development Team (QA/PM/Dev). Here's why:
            -Developer creates feature in current sprint
            -QA tests feature. During testing they find a new bug that was introduced as a result of the feature recently implimented.
            -QA creates case for bug
            -QA assigns bug to Dev team so that it can be fixed in the current sprint

            Notes:
            It's important that newly introduced bugs get fixed in the sprint in which they are introduced, otherwise, we'll never ship code.

            Does this make sense? It's such an obvious limitation of the current system that I'm slightly shocked that it has received such little attention.

            Ian Wright added a comment - This is very important for our Development Team (QA/PM/Dev). Here's why: -Developer creates feature in current sprint -QA tests feature. During testing they find a new bug that was introduced as a result of the feature recently implimented. -QA creates case for bug -QA assigns bug to Dev team so that it can be fixed in the current sprint Notes: It's important that newly introduced bugs get fixed in the sprint in which they are introduced, otherwise, we'll never ship code. Does this make sense? It's such an obvious limitation of the current system that I'm slightly shocked that it has received such little attention.

            The way we're using Jira it would be really useful to be able to move an item into a sprint without having to go to an agile board. Often our teams meet to discuss issues and end up using the issues filter screens to browse, for instance, and then we realize that to move a newly prioritized issue item into the current sprint we have to go to the agile board. Also, our developers create bugs against different products and it would be great for a project manager using a dashboard gadget to monitor incoming bugs could be able to move a new into the appropriate sprint.

            I said aloud to my cube mate just now: "how do you move something into the current sprint if you're not on the agile board?" and he said "I don't know, but let me know if you figure it out" and then the rest of the cubicle farm hooted "Me too!" in unison, like a tree full of birds or something.

            Javier Carey added a comment - The way we're using Jira it would be really useful to be able to move an item into a sprint without having to go to an agile board. Often our teams meet to discuss issues and end up using the issues filter screens to browse, for instance, and then we realize that to move a newly prioritized issue item into the current sprint we have to go to the agile board. Also, our developers create bugs against different products and it would be great for a project manager using a dashboard gadget to monitor incoming bugs could be able to move a new into the appropriate sprint. I said aloud to my cube mate just now: "how do you move something into the current sprint if you're not on the agile board?" and he said "I don't know, but let me know if you figure it out" and then the rest of the cubicle farm hooted "Me too!" in unison, like a tree full of birds or something.

            This seems to be pretty important for us, as I want to search for issues using JQL (not possible on Plan mode) and assign issues to Sprint based on that filer. So far I need to open each individual item, click "View on board", find it there and then put to sprint. very time consuming.

            Pavel Bulanov added a comment - This seems to be pretty important for us, as I want to search for issues using JQL (not possible on Plan mode) and assign issues to Sprint based on that filer. So far I need to open each individual item, click "View on board", find it there and then put to sprint. very time consuming.

              Unassigned Unassigned
              ttzidamis Theodore Tzidamis (Inactive)
              Votes:
              18 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: