+1

The 'Request Participants' field should be added to customer portal forms. It would be much easier for users to fill in this field before submitting the form, rather than having to explain to them that the ticket can be shared after submission.

This feature worked well on Data Centre, so why make the average user's life more difficult?

+12

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

Please add this feature,

Hi team,
any plans around that

Please add this feature. 

We need the system to auto add Request Participants based on Organization (customer) of certain support tickets please!!! 

A workaround that includes existing JSD Automation can be achieved via a webhook THEN action that could call JSD's own API https://docs.atlassian.com/jira-servicedesk/REST/4.9.0/#servicedeskapi/request/{issueIdOrKey}/participant-addRequestParticipants with the configured usernames. Please note, that you need to be running a JSD Server version 4.1 or higher.

Mandatory to deliver flexiblity to service desk in 24x7 with multiple teams involve in a faster incident resolution.  

I worked around this issue using vanilla Jira Cloud, multiple workflows (1 per issuetype/project) and post functions. The feature would be incredibly useful though. This method adds a lot of clutter.

Official Jira doc about it

This feature would be extremely useful with how we use the software.  Is this functionality still being considered?

Why isn't this already a feature of Service Desk?

Given I cannot batch 'Add Participant' to tickets, then this becomes yet another time-consuming job I have to do by hand... 

I think this would be very helpful feature to implement them.

I think that this is a common requirement of nearly all service desks. Companies frequently support entire teams of users on an "account" basis. Since no single individual can work 24-hour x 7day shifts uninterrupted, it frequently becomes important for ALL members of an account team to be aware of support requests.

(We actually run into this problem a lot with getsupport.atlassian.com - it is PAINFUL to remember to request the addition of all our team's email addresses every time we open a request!)

Having the ability to build "Teams" "Organizations" or "Accounts" in a service desk, then assigning User Groups from Jira/crowd, (or even better - custom user lists within the SD project) could be a really great way to implement this. Then the agent/admin could enable "Auto-add participants" for that team/org/account and JSD would auto-add them to any request that was opened by any user within that team/org/account group.

I predict that this feature would greatly improve efficiency in resolution of support requests...

Going back to the getsupport.atlassian.com examples, we frequently run into issues where Atlassian support teams are requesting more info or debug data, that could be gathered by any member of my team... but the only person with access to the ticket is the original requestor. If the rest of my team had been automatically copied, the response from us (Customer) could be up to 24hours faster.

I also encounter this difficulty in competitive systems (like Service-now). I think that the company to build this the soonest will open themselves to a whole new subset of customers in today's team-oriented, collaborative world!

I need this feature ASAP (Cloud Version)

Created four yers ago...uhhh....will wait for it)

Hoping my loan voice is heard .

Any idea on when or if this one will be looked at? Looks like an issue that is in demand and while I am no developer I would have thought reasonable simple to do.  You would make a lot of us very happy if you did .

To put forward a business case for us:
We have an AUD support desk and an a UK support desk. The UK support desk cannot move to Jira SD until we have this feature. For now they are using our old system that is clunky, but does do this feature. This means that people who are working on both services desks are using two systems. They love Jira, hate the old system, so really really want to move the UK to Jira. Please make them happy.

Thanks,

I have got to say - Do Jira actually do anything about these requests? A lot of great ideas and needed functionality but most of the ones I see are all years old.

I got a survey the other day on how to improve Jira - Simple answer - just solve some of these problems!! Add some Functionality instead of selling Add ons.

Is there a timeline for this feature making it to a released version?  We are using the server version.

Hi I need this in Cloud Version.

I'm rather puzzled the automation for Service Desk is so limited in what it can edit in an issue. Why? 

A lot of customers asking for this functionality. We are using server version.

Need this in the server version please.

We would like this option in the Cloud version of Jira Service Desk.

Hi I want this to add to a specific org some specific users.

I know there is the option of customers notification for added organisation. But this will notify all the users of all the orgs, and I only want one org.

Please include this functionality.

Please add this or the ability for all customers to see all issues in a project.

We need it in Server version

Hi,
I would like this option in cloud version

Is this not possible out of the box now? IIRC you need to do it on the workflow, not using the SD automation.

Please, add this in Server... this should be a default feature.

i want this option in cloud version

Sadly Actions for JIRA Service Desk is only available for Server instances not Cloud ones such as ours.

Hi,

You can use plugin Actions for JIRA Service Desk. From version 1.3.9 there is automation rule "Add Request Participants". You can also use it when issue is created. Here you can find more information: https://intenso.atlassian.net/wiki/display/AFJSD/Actions+1.3.9 

Best Regards

Same as JSD-270 ?

Just had request for such a feature from end user, so hopeful it will appear some day as a native feature.

nigel7 Thanks for the ScriptRunner suggestion, I have been looking at it but at $250 per month ( we are in the 500 users bracket) it is far too expensive.