Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1269

Allow to bulk change "Request participants"

XMLWordPrintable

    • 31
    • 7
    • We collect Jira Service Desk 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 Service Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.

      Summary

      There is no feature to bulk edit the "Request Participants" of a JIRA Service Desk Issue. Instead, when users attempt to edit the field using Bulk Edit, they experience an error stating "Bulk editing is not supported for Service Desk Request participants.". When users need to change the "Request participants" of multiple issues, they need to do it manually one by one.

      Steps to Reproduce

      1. Search for some Service Desk Issues
      2. Attempt to use the Bulk Edit > Edit feature
      3. Observe that there is no way to update the "Request Participants" as it is listed as an "Unavailable Action"

      Expected Results

      The ability to update the "Request Participants" field should be possible.

      Actual Results

      No such functionality exists in the product.

      Workarounds

      A possible workaround could be to use the REST API, or SQL directly on the JIRA Database. Note that Atlassian does not support customers performing direct data manipulation of application databases via queries such as INSERT, UPDATE or DELETE, as they can easily lead to data integrity problems. If Atlassian encounters manipulation or customisations at this level, we may ask customers to restore data from their last known working state, or to engage an Expert to help recover their instance to a supportable state. If you are confident your UPDATE or INSERT is safe and your change management system is reliable, refer to the specific product's database documentation.

          Form Name

            [JSDSERVER-1269] Allow to bulk change "Request participants"

            Scott Fannen added a comment -

            Follow up to Zev Ginzburg, that will replace the Request Participants (lucky I tested on one issue first), however, in the Edit Issue for Request Participant, you can (and in many cases should) and "copy from issue" from the choices AS WELL AS the people you want to add.

            This will add the EXISTING request participants, and the new ones.

            And yes, it's slightly crazy that bulk edit doesn't let you do Request Participants in any way yet.

            Scott Fannen added a comment - Follow up to Zev Ginzburg, that will replace the Request Participants (lucky I tested on one issue first), however, in the Edit Issue for Request Participant, you can (and in many cases should) and "copy from issue" from the choices AS WELL AS the people you want to add. This will add the EXISTING request participants, and the new ones. And yes, it's slightly crazy that bulk edit doesn't let you do Request Participants in any way yet.

            Zev Ginzburg added a comment -

            I have come up with a work around for this, not sure if it has been posted before:

            In your Service Desk's settings, open the AUTOMATION tool, and create a rule based on a Schedule.

             

            1. Select a the trigger "Scheduled"
              1. Enter in a time interval (and don't worry about a specific interval because this is a one time only job)
              2. Insert a condition based on a JQL
            2. Add "New Action"
              1. Edit issue
                1. Search "Request Participant"
                  1. Select a user to add
            3. Publish Rule
            4. Run the rule
              1. Check audit log to ensure automation ran correctly
            5. If the rule ran successfully TURN THE RULE OFF.

             

            This worked in our instance and is a much more user friendly way than potentially adding new fields, or manually adding a participant to a number of tickets.

             

            Thanks and I hope as of today, 338 votes can constitute enough gathered interest.

            Zev Ginzburg added a comment - I have come up with a work around for this, not sure if it has been posted before: In your Service Desk's settings, open the AUTOMATION tool, and create a rule based on a Schedule .   Select a the trigger "Scheduled" Enter in a time interval (and don't worry about a specific interval because this is a one time only job) Insert a condition based on a JQL Add "New Action" Edit issue Search "Request Participant" Select a user to add Publish Rule Run the rule Check audit log to ensure automation ran correctly If the rule ran successfully TURN THE RULE OFF .   This worked in our instance and is a much more user friendly way than potentially adding new fields, or manually adding a participant to a number of tickets.   Thanks and I hope as of today, 338 votes can constitute enough gathered interest.

            Allen Semerdjian added a comment - - edited
            • created a temporary field "TAG"

            automation job

            • if the field tag changes then edit issue
            • edit issue "request participants" Copy from issue & name1, & name2

            ran JQL query of what I wanted to update

            • bulk change, Edit field "TAG"

            executes the above job, appending the names added
            verify job log

            run JQL query of what I wanted to update + "TAG" field

            • bulk change, Edit field "TAG" remove

            remove the custom field from the screen schema, then finally the custom field itself

             

             

             

            Allen Semerdjian added a comment - - edited created a temporary field "TAG" automation job if the field tag changes then edit issue edit issue "request participants" Copy from issue & name1, & name2 ran JQL query of what I wanted to update bulk change, Edit field "TAG" executes the above job, appending the names added verify job log run JQL query of what I wanted to update + "TAG" field bulk change, Edit field "TAG" remove remove the custom field from the screen schema, then finally the custom field itself      

            Rui Neves added a comment -

            +1

            Rui Neves added a comment - +1

            Lutz Klabuhn added a comment -

            +1

            Lutz Klabuhn added a comment - +1

            Abhishek Marshetty added a comment -

            I was just looking for a solution to bulk-update the "Request participants" and ended up here. This feature was suggested in 2014 and is almost 8 years. @Jira, please review this suggestion and do the needful.

            Abhishek Marshetty added a comment - I was just looking for a solution to bulk-update the "Request participants" and ended up here. This feature was suggested in 2014 and is almost 8 years. @Jira, please review this suggestion and do the needful.

            Arvin M added a comment -

            This feature would be really nice to have. @Jira, please take a look at this request again. Thank you very much.

            Arvin M added a comment - This feature would be really nice to have. @Jira, please take a look at this request again. Thank you very much.

            Romain FOURNIER added a comment -

            This issue is open since 2014... It's a shame that 8 years after, it's not yet implemented...

            Shame shame shame on you...

            Romain FOURNIER added a comment - This issue is open since 2014... It's a shame that 8 years after, it's not yet implemented... Shame shame shame on you...

            Monica Morris added a comment -

            This is a critical feature for normal service desk operations. Would be particularly helpful for the workaround required to fix the impact of this known bug: https://jira.atlassian.com/browse/JSDCLOUD-7546

            Please add the functionality Atlassian!

            Monica Morris added a comment - This is a critical feature for normal service desk operations. Would be particularly helpful for the workaround required to fix the impact of this known bug: https://jira.atlassian.com/browse/JSDCLOUD-7546 Please add the functionality Atlassian!

            Daniel Salvat added a comment -

            +1

            Daniel Salvat added a comment - +1

              Unassigned Unassigned
              6e107d394ed3 Rodolfo
              Votes:
              375 Vote for this issue
              Watchers:
              154 Start watching this issue

                Created:
                Updated: