I'm trying to create new automation based on Portal groups, that will change Request participants when a new issue is created.
There is an option to do this?
Thanks in advance
I also agreed with what @Tansu Akdeniz stated, unfortunately it is not possible to achieve what you wanted with automation.
There was even an enhancement request to expose the portal group ID via JQL which was not being considered by Atlassian - https://jira.atlassian.com/browse/JSDCLOUD-3472.
The only recommendation that I can think of
1) Create separate request forms (even though they are the same in the setup), where you can then use automation to test against by the request form name. If you want to keep the name being the same, then you will need to setup some type of field which you can pre-populate with certain values, then you can further search for it at the issue level to differentiate the different requests.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
I am not quite understand your ask as you are trying to compart assignee.key with the request type description value?
With user object (Assignee) smart value properties are limited to the following -
accountId: the unique ID of the user, set by Jira. It is not possible to change this ID. Learn more about converting usernames to user account IDs.
active: whether the user's account is active or not
avatarUrls: provides access to the user's avatar images in sizes 16x16, 24x24, 32x32 & 48x48
displayName: the full name in the user's profile
emailAddress: the email address in the user's profile
timeZone : the time zone based on the location set in the user's profile.
Need a bit more information.
*The assignee.key in the picture is an example that came from Jira, I didn't write something there so its a blank (with an example built-in)
I'll explain, I have a project with some portal groups that contain some request types.
Some of the request types have the same name but they are different.
I want to create a new automatic rule that adds participants to specific Portal groups,
That is why I created this question in the first place.
Unfortunately, as Tansu wrote there is no option to check portal groups in the automation rule directly
So I added a Request type description for the different requests to compare the description to a value, as you can see in the picture that I added.
but I didn't find how to call the description using the Smart Value in Jira
Thank you for your help!
Unfortunately, Automation smart values doesn't have a way to obtain request type's description. Here are the available options for smart values against Request Type -
Accesses information from Jira Service Management requests.
- Returns the customer request type.
- Returns the status of the current request.
- Returns the customer request type for older Jira instances.
You will need to create a custom field and tag your request in different JSM projects, then use it to achieve your ask.