Creating issues in JIRA sets ranking inconsistently.

      Steps to Replicate the Problem:

      • Creating an Issue from a view other than the Planning Board (e.g. from the dashboard) causes the issue to appear at the bottom of the Planning View.
      • When creating it from the Planning View, the new ticket will automatically appear underneath whichever ticket is currently selected.
      • If no ticket is selected in the Planning View and a new ticket is added, that ticket will appear at the TOP of the backlog. To reproduce, just manually remove the selectedIssue=XXX query string parameter from the Planning View URL and try to create a new ticket.

      Expected Behavior:

      Creating a new issue should put it to the bottom of the backlog at all times, to prevent accidentally giving the issue a priority.

      Ref.: https://answers.atlassian.com/questions/198381/configuring-new-issue-planning-board-position

            [JSWSERVER-10472] "Create Issue" Sets Rank Randomly

            This ticket will be closed, as it does not seem to be a bug. A corresponding Suggestion ticket has been created here: JSW-10846. If you have any additional comments and/or suggestions, please add them to that ticket.

             

            Kind regards,

            The JIRA Software Team

            Marek Broda (Inactive) added a comment - This ticket will be closed, as it does not seem to be a bug. A corresponding Suggestion ticket has been created here:  JSW-10846 . If you have any additional comments and/or suggestions, please add them to that ticket.   Kind regards, The JIRA Software Team

            Gerald Fru added a comment -

            We also experience some weird behavior when creating an issue within Boards.
            It is not reproducible where the issue goes to the backlog, when someone creates it within the board view. Sometimes it gets on top, sometimes on bottom, sometimes in between other issues.

            Voted for this to be implemented

            BR Gerald

            Gerald Fru added a comment - We also experience some weird behavior when creating an issue within Boards. It is not reproducible where the issue goes to the backlog, when someone creates it within the board view. Sometimes it gets on top, sometimes on bottom, sometimes in between other issues. Voted for this to be implemented BR Gerald

            It would be great if new tickets went to the bottom of the backlog as default... or at least be an option.

            Christine Kahn added a comment - It would be great if new tickets went to the bottom of the backlog as default... or at least be an option.

            I would just comment, that I like the current behaviour. In our organization, the person creating the issue, typically also knows how it should be ranked. So being able to do both things in the same step is really nice. If all issues were automatically put at the button, the user would first need to create the issue, scroll to the buttom, and then drag it to the correct rank. So if this should be implemented, it should at least be so as an setting, so it would be possibly to chose between the current behaviour, and put everything to button behaviour, like suggested in GHS-10846.

            Anders Kreinøe added a comment - I would just comment, that I like the current behaviour. In our organization, the person creating the issue, typically also knows how it should be ranked. So being able to do both things in the same step is really nice. If all issues were automatically put at the button, the user would first need to create the issue, scroll to the buttom, and then drag it to the correct rank. So if this should be implemented, it should at least be so as an setting, so it would be possibly to chose between the current behaviour, and put everything to button behaviour, like suggested in GHS-10846 .

            Shouldn't this behaviour described above by Michael Elias be documented somewhere? Because I don't think it is.

            Evangelos Vrocharis added a comment - Shouldn't this behaviour described above by Michael Elias be documented somewhere? Because I don't think it is.

            fabian.ehrentraud, you can vote on GHS-10846 which is the new feature I created for this as per Michael's suggestion. As I'm the reporter of that, you should be able to vote on it.

            Matheus Fernandes added a comment - fabian.ehrentraud , you can vote on GHS-10846 which is the new feature I created for this as per Michael's suggestion. As I'm the reporter of that, you should be able to vote on it.

            I would upvote, but I can't as I'm the reporter

            Fabian Ehrentraud added a comment - I would upvote, but I can't as I'm the reporter

            kevin13, I've created a new feature regarding this here: https://jira.atlassian.com/browse/GHS-10846

            Please vote on this to increase its popularity as per our Implementation of New Features Policy.

            Matheus Fernandes added a comment - kevin13 , I've created a new feature regarding this here: https://jira.atlassian.com/browse/GHS-10846 Please vote on this to increase its popularity as per our Implementation of New Features Policy .

            Hi Michael, thank you for the quick the reply. I don't understand why there is a difference in behaviour between creating a new Issue from the Work Mode as opposed to the Plan Mode? Why do you put a new Issue on the bottom of the Backlog when it is created in the Work Mode but on the top when in the Plan Mode, this is confusing me? A New Issue needs to be prioritised and hence a human decision (typically the PO) is made to place it in a particular place on the Backlog. It makes sense to me to thus by default to place it at the bottom of the Backlog in all cases. Even placing it under a selected Issue confuses me, but now that I know this is how it works I will select the bottom most Issue when creating a new Issue in Plan Mode.

            Please provide instructions how to log a Feature Request for this issue?

            Thank you
            Kevin

            Deleted Account (Inactive) added a comment - Hi Michael, thank you for the quick the reply. I don't understand why there is a difference in behaviour between creating a new Issue from the Work Mode as opposed to the Plan Mode? Why do you put a new Issue on the bottom of the Backlog when it is created in the Work Mode but on the top when in the Plan Mode, this is confusing me? A New Issue needs to be prioritised and hence a human decision (typically the PO) is made to place it in a particular place on the Backlog. It makes sense to me to thus by default to place it at the bottom of the Backlog in all cases. Even placing it under a selected Issue confuses me, but now that I know this is how it works I will select the bottom most Issue when creating a new Issue in Plan Mode. Please provide instructions how to log a Feature Request for this issue? Thank you Kevin

            Hi All,

            The current behaviour when creating issues on plan mode is a follows:

            • When 1 or more issues have been selected -> rank the new issue after the lowest ranked selected issue
            • When no issue is selected -> rank the issue at the top of where the plan mode is currently scrolled.

            When not on plan mode, new issues are ranked to the bottom of the backlog

            The behaviour on plan mode when no issues are selected is what is causing the confusion here I believe. We added this behaviour because we believe it is a better experience than dropping the issue to the bottom of the backlog. Now this issue is placed where the user is currently viewing the backlog and he can rank the issue accordingly.

            You may create a feature request in this project if you wish to see this behaviour changed in the future. We'll evaluate the request, but cannot guarantee that we will change the current behaviour.

            Regards,
            JIRA Agile team

            MichaelA (Inactive) added a comment - Hi All, The current behaviour when creating issues on plan mode is a follows: When 1 or more issues have been selected -> rank the new issue after the lowest ranked selected issue When no issue is selected -> rank the issue at the top of where the plan mode is currently scrolled. When not on plan mode, new issues are ranked to the bottom of the backlog The behaviour on plan mode when no issues are selected is what is causing the confusion here I believe. We added this behaviour because we believe it is a better experience than dropping the issue to the bottom of the backlog. Now this issue is placed where the user is currently viewing the backlog and he can rank the issue accordingly. You may create a feature request in this project if you wish to see this behaviour changed in the future. We'll evaluate the request, but cannot guarantee that we will change the current behaviour. Regards, JIRA Agile team

            Michael Elias [Atlassian] could you provide me with an update on this issue? Do you know if there was a Support ticket logged? I don't want to log another in case it has been logged.

            I want to log an Enhancement Request as a result of this Bug,
            https://jira.atlassian.com/browse/GHS-10472

            When I go to https://support.atlassian.com
            and end up at https://support.atlassian.com/customer/home
            I get a message saying, “support.atlassian.com has been updated to use JIRA Service Desk.”

            If I click through to “JIRA Service Desk” I end up at https://www.atlassian.com/software/jira/service-desk where I get the info on the Service Desk Product. I cannot log any Issues from here.

            If I follow the link lower down on the https://support.atlassian.com/customer/home page and go to “Bug Tracker” to “request a feature” I end up on the System Dashboard. If I Create Issue from here I get presented with,

            “Support Requests are no longer handled by this system.
            As part of our ongoing effort to streamline support and make it a fairer system we are trying to centralise all support.
            Please create all Support Requests on our Support System . If you have not used our support service before you will need to sign up for a new account.
            If you have been directed here by any documentation, please let us know in your support ticket and we will update the documentation.
            Sorry for any inconvenience.
            Cheers,
            Atlassian Support Manager”

            Please provide instructions how to log a Feature Request for this issue, if not already?

            Thank you
            Kevin

            Deleted Account (Inactive) added a comment - - edited Michael Elias [Atlassian] could you provide me with an update on this issue? Do you know if there was a Support ticket logged? I don't want to log another in case it has been logged. I want to log an Enhancement Request as a result of this Bug, https://jira.atlassian.com/browse/GHS-10472 When I go to https://support.atlassian.com and end up at https://support.atlassian.com/customer/home I get a message saying, “support.atlassian.com has been updated to use JIRA Service Desk.” If I click through to “JIRA Service Desk” I end up at https://www.atlassian.com/software/jira/service-desk where I get the info on the Service Desk Product. I cannot log any Issues from here. If I follow the link lower down on the https://support.atlassian.com/customer/home page and go to “Bug Tracker” to “request a feature” I end up on the System Dashboard. If I Create Issue from here I get presented with, “Support Requests are no longer handled by this system. As part of our ongoing effort to streamline support and make it a fairer system we are trying to centralise all support. Please create all Support Requests on our Support System . If you have not used our support service before you will need to sign up for a new account. If you have been directed here by any documentation, please let us know in your support ticket and we will update the documentation. Sorry for any inconvenience. Cheers, Atlassian Support Manager” Please provide instructions how to log a Feature Request for this issue, if not already? Thank you Kevin

            What currently happens is this,

            1. If a Story is created from within the Work Mode Dashboard it is by default created on the Backlog and placed at the bottom, this is correct behaviour.
            2. However, from within the Plan Mode Dashboard it behaves somewhat differently,
            a. If a Backlog Story is selected (pale blue highlight) the new Story is displayed directly underneath it.
            b. If a Story in a Sprint is selected the new Story is displayed on the top of the Backlog.
            c. If no Story in a Sprint is selected the new Story is displayed on the top of the Backlog (you can simulate this by removing the eg. “&selectedIssue=TESTSTORY-1234” from the URL).
            d. Therefore the only way to get a new Story to display on the bottom of the Backlog is to select the bottom Story and then Create the new Story.

            I tried changing the default behaviour by modifying the filter however the Rank search order is the only way that allows the ability to then manually ‘drag and drop’ the Stories to another order, any other sort order prevents the ability to change the order manually.

            I would like the Backlog to work like this,

            1. All new Stories are by default created on the Backlog (as is now) but always added to the bottom of the list.
            2. The Product Owner, who owns the Backlog, then drags and drops the Stories during regular Backlog Grooming to the order that he wants.

            Deleted Account (Inactive) added a comment - - edited What currently happens is this, 1. If a Story is created from within the Work Mode Dashboard it is by default created on the Backlog and placed at the bottom, this is correct behaviour. 2. However, from within the Plan Mode Dashboard it behaves somewhat differently, a. If a Backlog Story is selected (pale blue highlight) the new Story is displayed directly underneath it. b. If a Story in a Sprint is selected the new Story is displayed on the top of the Backlog. c. If no Story in a Sprint is selected the new Story is displayed on the top of the Backlog (you can simulate this by removing the eg. “&selectedIssue=TESTSTORY-1234” from the URL). d. Therefore the only way to get a new Story to display on the bottom of the Backlog is to select the bottom Story and then Create the new Story. I tried changing the default behaviour by modifying the filter however the Rank search order is the only way that allows the ability to then manually ‘drag and drop’ the Stories to another order, any other sort order prevents the ability to change the order manually. I would like the Backlog to work like this, 1. All new Stories are by default created on the Backlog (as is now) but always added to the bottom of the list. 2. The Product Owner, who owns the Backlog, then drags and drops the Stories during regular Backlog Grooming to the order that he wants.

            • If you do not make a selection, the issue is put on top of the backlog (and this would still be nice to have: that the new issue is put at the bottom of the backlog)

            I agree that new issues should be put on the bottom of the backlog by default.

            Fabian Ehrentraud added a comment - If you do not make a selection, the issue is put on top of the backlog (and this would still be nice to have: that the new issue is put at the bottom of the backlog) I agree that new issues should be put on the bottom of the backlog by default.

            Nihal Cakir added a comment - - edited

            We have lately updated to Jira Agile Version 6.3.11.0 and this is not a problem anymore.
            When creating an issue, you can now select a sprint (I've attached a screenshot)

            • If selecting the current sprint, you will get a warning message (see screenshot), that this affects the current sprint.
            • If selecting a future sprint, everything is okay.
            • If you do not make a selection, the issue is put on top of the backlog (and this would still be nice to have: that the new issue is put at the bottom of the backlog)

            Nihal Cakir added a comment - - edited We have lately updated to Jira Agile Version 6.3.11.0 and this is not a problem anymore. When creating an issue, you can now select a sprint (I've attached a screenshot) If selecting the current sprint, you will get a warning message (see screenshot), that this affects the current sprint. If selecting a future sprint, everything is okay. If you do not make a selection, the issue is put on top of the backlog (and this would still be nice to have: that the new issue is put at the bottom of the backlog)

            Matt Zembruski added a comment - - edited

            Our team is experiencing this exact same issue, and we're currently using Atlassian JIRA v6.3.1. Is this issue now resolved in a patch release? We'd like to get it resolved ASAP since it causes confusion in our product backlog. Thank you.

            Matt Zembruski added a comment - - edited Our team is experiencing this exact same issue, and we're currently using Atlassian JIRA v6.3.1. Is this issue now resolved in a patch release? We'd like to get it resolved ASAP since it causes confusion in our product backlog. Thank you.

            Hi,
            Could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. The credentials to access the Support site should be the same as this one (jira.atlassian.com).
            Regards,
            JIRA Agile Team

            MichaelA (Inactive) added a comment - Hi, Could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. The credentials to access the Support site should be the same as this one (jira.atlassian.com). Regards, JIRA Agile Team

              Unassigned Unassigned
              6685795f6817 Fabian Ehrentraud
              Affected customers:
              16 This affects my team
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: