Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-85718

Ability to transition issues using drag and drop to another status is in the same column

    • 31
    • 21
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      In combination with a keyboard modifier, provide the ability to transition an issue when statuses are on the same column on a board. Currently, users have to resort to the "." shortcut or the detail's view Workflow actions drop down. It would be nice to support the drag & drop UI paradigm for all available transitions.

            [JRACLOUD-85718] Ability to transition issues using drag and drop to another status is in the same column

            Josh added a comment -

            Please reconsider this functionality.

            As Atlassian continues to move into other areas of the business beyond IT and agile teams (looking at you HR, Finance, etc.), the commitment to the dogma of each column representing only a single status makes much less sense. It comes down to UI simplicity for business teams:

            • If you have more than 5 or so statuses, having a 1:1 relationship between columns and statuses makes poor usage of screen real estate and can make users have to resort to horizontal scrolling just to move through the workflow
            • By allowing horizontal AND vertical movement across the board (we call this "matrix mode"), it is a better use of screen real estate with no scrolling needed

            Josh added a comment - Please reconsider this functionality. As Atlassian continues to move into other areas of the business beyond IT and agile teams (looking at you HR, Finance, etc.), the commitment to the dogma of each column representing only a single status makes much less sense. It comes down to UI simplicity for business teams: If you have more than 5 or so statuses, having a 1:1 relationship between columns and statuses makes poor usage of screen real estate and can make users have to resort to horizontal scrolling just to move through the workflow By allowing horizontal AND vertical movement across the board (we call this "matrix mode"), it is a better use of screen real estate with no scrolling needed

            Hello all, as has been pointed out many times, this issue has been open for 13 years at this point. Every team I've been on has asked for this and we've always just accepted that you can't do it, but it's annoying. I thought it was dumb you couldn't do this about 7 years ago when I started using Jira at my very first job, but I accepted it as something that would be fixed "eventually." However, it wasn't until today that I re-encountered this issue and got so annoyed by it that I finally took the time to insist to myself this must be possible (because I refused to believe that a bug this easy to fix wasn't ever done) and dig through the internet until I finally found this issue. I guarantee most people are not motivated enough by this bug/missing functionality to do this, but I think the number of people that would be impacted by it is orders of magnitude more than the votes on this issue (for funsies, can anyone internally pull metrics on how many people have a board with more than one status in the same column? That's the number of users whose lives could be improved by completing this and I'm willing to bet large amounts of money that it's a significant portion of the user base; especially power users/advocates). The lack of this seemingly tiny feature has forced the teams I've been on to simplify our workflows and use comments on tickets and other less-optimal things to indicate the status of the tickets instead of using the status field itself because transitioning them within the same column is a pain and having 7+ columns on one board is completely impractical unless everyone has an ultrawide.

            I don't think this is a huge pain point for a lot of teams since there are fairly easy work-arounds for it (open issues in new windows, transition in the side window, etc.) but this is one of the most glaring (of a probably large number) of "mosquito bite" type issues that contributes to Jira being seen as a very powerful, but often frustrating tool to use. As has been demonstrated by the multiple plugins, JSX hacks, and other workarounds people have come up with to solve this problem, it's not a technically difficult problem to solve nor does it take much time to solve. So can someone please scratch this itch and just knock it out during a hackathon or something? Or hell, hire me for a week, let me fix it, and then get back to solving other problems .

            Kenny Loveall added a comment - Hello all, as has been pointed out many times, this issue has been open for  13 years at this point. Every team I've been on has asked for this and we've always just accepted that you can't do it, but it's annoying. I thought it was dumb you couldn't do this about 7 years ago when I started using Jira at my very first job, but I accepted it as something that would be fixed "eventually." However, it wasn't until today that I re-encountered this issue and got so annoyed by it that I finally took the time to insist to myself this must be possible (because I refused to believe that a bug this easy to fix wasn't ever done) and dig through the internet until I finally found this issue. I guarantee most people are not motivated enough by this bug/missing functionality to do this, but I think the number of people that would be impacted by it is orders of magnitude more than the votes on this issue (for funsies, can anyone internally pull metrics on how many people have a board with more than one status in the same column? That's the number of users whose lives could be improved by completing this and I'm willing to bet large amounts of money that it's a significant portion of the user base; especially power users/advocates). The lack of this seemingly tiny feature has forced the teams I've been on to simplify our workflows and use comments on tickets and other less-optimal things to indicate the status of the tickets instead of using the status field itself because transitioning them within the same column is a pain and having 7+ columns on one board is completely impractical unless everyone has an ultrawide. I don't think this is a huge pain point for a lot of teams since there are fairly easy work-arounds for it (open issues in new windows, transition in the side window, etc.) but this is one of the most glaring (of a probably large number) of "mosquito bite" type issues that contributes to Jira being seen as a very powerful, but often frustrating tool to use. As has been demonstrated by the multiple plugins, JSX hacks, and other workarounds people have come up with to solve this problem, it's not a technically difficult problem to solve nor does it take much time to solve. So can someone please scratch this itch and just knock it out during a hackathon or something? Or hell, hire me for a week, let me fix it, and then get back to solving other problems .

            Hi! I also have several statuses per column. So please consider this feature for being implemented.

            Nataliia Sosnovshchenko added a comment - Hi! I also have several statuses per column. So please consider this feature for being implemented.

            Hello, is there any chance that this feature will come soon?
            It's pretty bad that this feature isn't supported, because why can I group status in a column but then don't move the ticket

            Melanie Röver (Admin) added a comment - Hello, is there any chance that this feature will come soon? It's pretty bad that this feature isn't supported, because why can I group status in a column but then don't move the ticket

            I agree, our workflow has many steps (statuses) at a high resolution, however we use the Kanban board to illustrate the lower resolution workflow. Here is an example illustrating what I mean. Being able to transition between statuses in the same Kanban column would help reduce process friction.

             

            Lance Caraccioli added a comment - I agree, our workflow has many steps (statuses) at a high resolution, however we use the Kanban board to illustrate the lower resolution workflow. Here is an example  illustrating what I mean. Being able to transition between statuses in the same Kanban column would help reduce process friction.  

            definitely would help

            Christian Giroux added a comment - definitely would help

            Bump

            Alexander Hirt added a comment - Bump

            Bump, any update?

            Ivan Ermakov added a comment - Bump, any update?

            Bump. Any updates so far?

            Alexander Borisov added a comment - Bump. Any updates so far?

            I cosign/second this. Thanks.

            Jason Luttrell added a comment - I cosign/second this. Thanks.

              Unassigned Unassigned
              38754ddc40c7 angel
              Votes:
              215 Vote for this issue
              Watchers:
              131 Start watching this issue

                Created:
                Updated: