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

As an user, I want the issue detail view to keep closed when changing sprints

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

      Current behaviour

      If I close the issue detail view, it will stay closed if I click on a ticket within the same sprint, but clicking on one issue from a different sprint will reopen the detail view.

      Expected behaviour

      We want the ability to enable/disable the detail view if needed.

          Form Name

            [JSWSERVER-10917] As an user, I want the issue detail view to keep closed when changing sprints

            legosarecool - I've now added some details in a comment on GHS-11160.

            Martin (Inactive) added a comment - legosarecool - I've now added some details in a comment on GHS-11160 .

            Thanks for the clarification, Martin.

            While it is possible to select the ticket with ctrl/cmd+click, it comes with it's own set of frustrations. Since it's add/remove to selection(as opposed to select), you have to ensure that the previous issue is unselected, or an issue in another 'group' won't be selected. :-/. This makes using the edit and operations dialog cumbersome as you have to de-select your previous card.

            As you said, this is more about disabling the detail view, so I'll start commenting more in GHS-11160. If you don't mind weighing in over there, it would help to have some more info on the philosophy behind the current behavior.

            Matthew Gray added a comment - Thanks for the clarification, Martin. While it is possible to select the ticket with ctrl/cmd+click, it comes with it's own set of frustrations. Since it's add/remove to selection(as opposed to select), you have to ensure that the previous issue is unselected, or an issue in another 'group' won't be selected. :-/. This makes using the edit and operations dialog cumbersome as you have to de-select your previous card. As you said, this is more about disabling the detail view, so I'll start commenting more in GHS-11160 . If you don't mind weighing in over there, it would help to have some more info on the philosophy behind the current behavior.

            Since this issue was focussed (mostly) on the inconsistent behaviour between different sprint, which is now fixed, I will resolve this and suggest anyone requesting the feature to disable/enable detail view opening to follow, vote and/or comment on the linked issue GHS-11160

            Regards,
            Martin
            JIRA Agile

            Martin (Inactive) added a comment - Since this issue was focussed (mostly) on the inconsistent behaviour between different sprint, which is now fixed, I will resolve this and suggest anyone requesting the feature to disable/enable detail view opening to follow, vote and/or comment on the linked issue GHS-11160 Regards, Martin JIRA Agile

            The expected behaviour, in JIRA Agile 6.6, is as follows:
            Clicking on the card will open the detail view.
            Ctrl+Click (Windows) or Cmd+Click (OSX) will not open the detail view.

            There was an inconsistency in earlier versions of JIRA Agile when clicking issues in the same sprint versus a different sprint, this is now fixed.

            Martin (Inactive) added a comment - The expected behaviour, in JIRA Agile 6.6, is as follows: Clicking on the card will open the detail view. Ctrl+Click (Windows) or Cmd+Click (OSX) will not open the detail view. There was an inconsistency in earlier versions of JIRA Agile when clicking issues in the same sprint versus a different sprint, this is now fixed.

            Hi Martin,

            Could you clarify what the expected behavior is?

            Matthew Gray added a comment - Hi Martin, Could you clarify what the expected behavior is?

            Reopening this to investigate inconsistent behaviour.

            Martin (Inactive) added a comment - Reopening this to investigate inconsistent behaviour.

            Hi, I'd also like to chime in and say this is a major frustration. The old behavior made sense, and it seems like this is a bit of 'dumbing down' the interface. I'd like to request for a board option to bring back the previous behavior. (It seems we're not alone, per GHS-11160)

            Martin, the suggested work around doesn't seem to work, at least on Chrome/OSX. None of the click modifiers do:

            1. Command Click acts as add/remove selection. Furthermore, you can only select a card if it is in the same column/swimlane as the one that is currently selected.
            2. Shift Click acts as select to
            3. Alt Click is the same as Click
            4. Command Click opens the mouse menu for the card.

            As it stands, I can't find a way to click on the board without dealing with the frustration of the details pane coming up and disrupting my focus. Please offer a solution!

            Matthew Gray added a comment - Hi, I'd also like to chime in and say this is a major frustration. The old behavior made sense, and it seems like this is a bit of 'dumbing down' the interface. I'd like to request for a board option to bring back the previous behavior. (It seems we're not alone, per GHS-11160 ) Martin, the suggested work around doesn't seem to work, at least on Chrome/OSX. None of the click modifiers do: Command Click acts as add/remove selection. Furthermore, you can only select a card if it is in the same column/swimlane as the one that is currently selected. Shift Click acts as select to Alt Click is the same as Click Command Click opens the mouse menu for the card. As it stands, I can't find a way to click on the board without dealing with the frustration of the details pane coming up and disrupting my focus. Please offer a solution!

            Whoa I really don't like this. I don't like seeing the detail view. Anyway to make this change user configurable?

            And if you decide to do it could you also make the issue link action configurable so that it opens the issue instead of just showing the detail view.

            Jon Pokrzyk added a comment - Whoa I really don't like this. I don't like seeing the detail view. Anyway to make this change user configurable? And if you decide to do it could you also make the issue link action configurable so that it opens the issue instead of just showing the detail view.

            There has been a change to the behaviour for opening the detail view to assist with users struggling to discover the previous behaviour of clicking on the issue key.
            Clicking an issue will open the detail view if it is closed.
            To avoid opening the detail view, please now use command-click when selecting an issue.

            Martin (Inactive) added a comment - There has been a change to the behaviour for opening the detail view to assist with users struggling to discover the previous behaviour of clicking on the issue key. Clicking an issue will open the detail view if it is closed. To avoid opening the detail view, please now use command-click when selecting an issue.

              Unassigned Unassigned
              pschaff Pietro Schaff (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: