Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-16420

Allow transitions for multiple issues on status with screen

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Classic - Boards
    • None
    • 1
    • 4
    • 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.

      At the moment, it is not allowed to drag and drop multiple issues at one time if the destination column is mapped to workflow status with a transition screen configured. This requires users to drag and drop issues one at a time.

      To replicate :

      • Configure the Done status to have a transition screen in the workflow.
      • Map the Done status to a Board column
      • Try drag and drop multiple issues at one time to that board

      Result :

      Message : Unable to transition multiple issues to Done. The transition screen is not supported when transitioning multiple issues.

      It would be useful to allow this feature for cases where a bulk update of issues is needed on Software boards.

        1. drag.png
          drag.png
          114 kB

            [JSWCLOUD-16420] Allow transitions for multiple issues on status with screen

            Simple usecase we have every day: a dev wants to pick several sub-tasks at once...

            Stefan Simon added a comment - Simple usecase we have every day: a dev wants to pick several sub-tasks at once...

            Have team members here that are constantly annoyed by the lack of this support. I can understand it in the event of different issue types that can use different screens between transitions – but even lacking the support for the same issue type is a pretty lacking feature.

            Michael J. Wyatt added a comment - Have team members here that are constantly annoyed by the lack of this support. I can understand it in the event of different issue types that can use different screens between transitions – but even lacking the support for the same issue type is a pretty lacking feature.

            I'm working with a client who really needs this feature.  They have field service techs who perform multiple service operations at a time and need a simple way to close them all, leaving the same comment on each.  They also want to be able to add the same attachment to each issue.  I know it's an edge case, but it seems like an elegant solution might be the following:

            When the user drags multiple issues on a board:

            • Display a screen with any fields that are common to all of the issue types.
            • If screens are present for the others, have a section for each issue (collapsed by default) that, when expanded, displays the fields for that screen/issue type.

            That would solve for my client's use case because they only need the comment and attachment field, which can be common to all issues.  They would never have to expand the other sections, unless there was a required field on one of them.  If that were the case, that section could be bubbled to the top and expanded by default.

            They require the use of a board (instead of issue navigator) for their service techs because they want to keep it as simple as possible.  Also, they would never give bulk edit permissions to their techs because the aren't really Jira savvy and could easily cause serious damage.

            They don't want to use Jira Service Desk at this time - Just Jira Software.

            Just some of my thoughts...

            Trevan Householder_Isos-Tech-Consulting_ added a comment - - edited I'm working with a client who really needs this feature.  They have field service techs who perform multiple service operations at a time and need a simple way to close them all, leaving the same comment on each.  They also want to be able to add the same attachment to each issue.  I know it's an edge case, but it seems like an elegant solution might be the following: When the user drags multiple issues on a board: Display a screen with any fields that are common to all of the issue types. If screens are present for the others, have a section for each issue (collapsed by default) that, when expanded, displays the fields for that screen/issue type. That would solve for my client's use case because they only need the comment and attachment field, which can be common to all issues.  They would never have to expand the other sections, unless there was a required field on one of them.  If that were the case, that section could be bubbled to the top and expanded by default. They require the use of a board (instead of issue navigator) for their service techs because they want to keep it as simple as possible.  Also, they would never give bulk edit permissions to their techs because the aren't really Jira savvy and could easily cause serious damage. They don't want to use Jira Service Desk at this time - Just Jira Software. Just some of my thoughts...

            Yes, missing this feature desperately. I could see it either ask for every single issue or bulk set the values.

            Alternatively it could simply ignore the issue screen. Admins could use conditions to prevent certain transitions without showing the screen.

            Prefer Administrator added a comment - Yes, missing this feature desperately. I could see it either ask for every single issue or bulk set the values. Alternatively it could simply ignore the issue screen. Admins could use conditions to prevent certain transitions without showing the screen.

            Quite a surprise for me, too.  I recall the ability to do this in the past.  Good thing I have bulk edit permission

            Greg Sarcona added a comment - Quite a surprise for me, too.  I recall the ability to do this in the past.  Good thing I have bulk edit permission

            Transition screens work with single issues. I'd expect the behaviour with multiple issues to set all issue fields to the values entered in the screen.

            Mark Malyon added a comment - Transition screens work with single issues. I'd expect the behaviour with multiple issues to set all issue fields to the values entered in the screen.

              Unassigned Unassigned
              rmacalinao Ramon M
              Votes:
              46 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated: