Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,145
Community Members
 
Community Events
176
Community Groups

Automation for adding requested participant based on the reporting user

Hi all,

I would like to create an automation that adds the individual that opened the incident to be added as a requested participant into the ticket.

I found this article, but I have very little familiarity with JQL so I am not sure how I can amend the value provided to reflect what I need. 

How to add/update Request Participants using Automation for Jira | Jira | Atlassian Documentation

I assume I need to use this JSON:

{"update": {
  "Request participants": [
   {
    "add": {"id":"<accountId>"}
   }
  ]
 }
}



And replace the section within the "add" line with {{reporter.displayname}} somehow, but not entirely sure.

Any assistance would be great. Thanks!

1 answer

1 accepted

0 votes
Answer accepted

@Alex S -

Hi Alex:

By default, users who created the issue doesn't need added to request participants since he/she is the issue reporter in JSM.  Can you provide why you want to the reporter to the requested participants for the same ticket?

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Yes, the users will get notified but they won't see all the details of the ticket unless they are a participant. There was an ask from leadership to have more transparency and visibility on certain ticket types so the requestor can monitor progress beyond email notification.

That is unfortunately a misconception, @Alex S. A request participant does not have any additional permissions in comparison to the reporter. All this is for, is to add a backup person for the ticket to follow and participate in comments.

If a user needs to see the full details of a ticket (i.e. all the internal information of a ticket, not just the information provided on creation and the comments that are exchanged afterwards), your users should have a proper Jira license and access your tickets internally, not from the customer portal. 

As long as it is ticket progress that you are referring to, tickets have a customer facing status, which represents the stage in the ticket workflow as you want it to be seen by customers. However, that is the status the reporter can see as well from the my requests page in the customer portal. So no need/use to add the reporter as a request participant there either. That would be - as @Joseph Chung Yin mentioned - entirely redundant.

Ah gotcha, well secondly the reason for this is because we have automations setup to create tickets in another project spurned off the initial request. And the only way I can think to link the individual to the new ticket is by automating that the individual will be a requested participant on the new one. Let me lay it out.
1. User creates ticket in project #1.

2. User is auto-added as participant.

3. Ticket is automatically created in project #2.

4. Automation also adds the user to the second ticket in project #2 as a participant.

The automation to add the user as a participant in project #2 states that it will copy the participants from the triggering issue (ticket in project #1). I couldnt think of another way to ensure the user knows and can track the second ticket thats created.

This is all kind of convoluted, but we need to ensure the user that created the ticket in our project is aware of and able to track the second ticket thats automatically created in the other project.

@Alex S -

Thanks for your update.  For your automation in issue creation in project #2, you can simply refer to the issue reporter of project #1 and use the reporter information when you populate the "requested participant" or "watcher" for the project #2 issue.  You should not have to do anything with the issue in project #1 (i.e. adding the reporter also as the participant of the same issue).

Best, Joseph

OK I poked around, I see I can set the reporter on the automated ticket for project #2. I set to copy from triggered issue which I am assuming is the ticket in project #1.

@Alex S -

Excellent.  If my suggestion helped you, please click on Accept answer when you have a chance.

Best, Joseph

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS

Atlassian Community Events