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

As a user, I can key in name for Custom Field "Sprint" name, rather than ID.

XMLWordPrintable

    • 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.

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

      By default, Custom Field "Sprint" only allowed to input Sprint ID such as 1,2,3,4 and etc. However, it is not very user friendly because you have to map this id with the sprint in your mind. For example, id 6 = Sprint 16.

      It would be great to be able to add an issue to sprints from the create/edit issues screen by name and not id.

          Form Name

            [JSWSERVER-7573] As a user, I can key in name for Custom Field "Sprint" name, rather than ID.

            Eric Pederson added a comment -

            Dear all: Please vote for GHS-10651 which fixes the same problem in the Bulk Edit feature.

            Eric Pederson added a comment - Dear all: Please vote for GHS-10651 which fixes the same problem in the Bulk Edit feature.

            Martin (Inactive) added a comment -

            chl, please follow this issue: https://jira.atlassian.com/browse/GHS-7255

            Martin (Inactive) added a comment - chl , please follow this issue: https://jira.atlassian.com/browse/GHS-7255

            Christen Lorensen added a comment -

            We just upgraded,work good.

            It would be nice if you could use the field in basic mode in issue search. Maybe you have plans for that later?

            Christen Lorensen added a comment - We just upgraded,work good. It would be nice if you could use the field in basic mode in issue search. Maybe you have plans for that later?

            Christen Lorensen added a comment -

            I forgot: Happy birthday, dear issue
            Even better today: Happy: you got solved

            Christen Lorensen added a comment - I forgot: Happy birthday, dear issue Even better today: Happy: you got solved

            Martin (Inactive) added a comment - - edited

            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 - - edited 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

            Tom Kotecki (Inactive) added a comment -

            Hi All,

            Many thanks for your feedback and votes on this issue, I wanted to provide an update for you: we have now scheduled work on this and aim to get it to you within a month or so. I will update this issue again once the fix is available for download.

            Kind regards
            Tom Kotecki
            Product Manager, JIRA Agile

            Tom Kotecki (Inactive) added a comment - Hi All, Many thanks for your feedback and votes on this issue, I wanted to provide an update for you: we have now scheduled work on this and aim to get it to you within a month or so. I will update this issue again once the fix is available for download. Kind regards Tom Kotecki Product Manager, JIRA Agile

            Deleted Account (Inactive) added a comment -

            It really is unacceptable that people must figure out the sprint ID, both because of the extra time, labor, and attention, and because of the high error rate. We name our sprints so they make sense to people, rather than forcing our people to adapt to JIRA. We need this ability when editing individual issues and when making bulk changes. This feature's absence combines with the inability to suppress email notifications of sprint assignment changes (except when bulk editing) to result in email bombardment. Those two deficiencies make it difficult for us to convince more teams to use JIRA.

            Deleted Account (Inactive) added a comment - It really is unacceptable that people must figure out the sprint ID, both because of the extra time, labor, and attention, and because of the high error rate. We name our sprints so they make sense to people, rather than forcing our people to adapt to JIRA. We need this ability when editing individual issues and when making bulk changes. This feature's absence combines with the inability to suppress email notifications of sprint assignment changes (except when bulk editing) to result in email bombardment. Those two deficiencies make it difficult for us to convince more teams to use JIRA.

            Gregory Demotchkine added a comment -

            @Ben - If sprint field is present on your edit screen, than you can edit the sprint using structure, (alas, you have to key in the sprint id, but hey I'm training my memory every day! )

            Gregory Demotchkine added a comment - @Ben - If sprint field is present on your edit screen, than you can edit the sprint using structure, (alas, you have to key in the sprint id, but hey I'm training my memory every day! )

            BenP added a comment -

            same here.. as soon as you have more than 1 project on the JIRA instance, this becomes a pressing issue!
            I'd also like to add another use case of editing sprint indication using (almworks) structure plugin.

            BenP added a comment - same here.. as soon as you have more than 1 project on the JIRA instance, this becomes a pressing issue! I'd also like to add another use case of editing sprint indication using (almworks) structure plugin.

            Gregory Demotchkine added a comment -

            Agree with the comments here, unbelievable that the issue still not resolved.
            I have to 'defend' Jira before my colleagues, saying, yeah, they wanted people to assign issues to sprints using JiraAgile and not issue Create/Edit... that's quite time wasting...
            What would be really great is to have 2 things in the issue Edit form:

            • Choose Sprint by Sprint name
            • Use a combobox to choose : send to top of the sprint, send to the botom of the sprint. - These are really two most common scenarios!

            Gregory Demotchkine added a comment - Agree with the comments here, unbelievable that the issue still not resolved. I have to 'defend' Jira before my colleagues, saying, yeah, they wanted people to assign issues to sprints using JiraAgile and not issue Create/Edit... that's quite time wasting... What would be really great is to have 2 things in the issue Edit form: Choose Sprint by Sprint name Use a combobox to choose : send to top of the sprint, send to the botom of the sprint. - These are really two most common scenarios!

              Unassigned Unassigned
              ckimloong John Chin
              Votes:
              76 Vote for this issue
              Watchers:
              58 Start watching this issue

                Created:
                Updated:
                Resolved: