Gor Greyan Expert

{ "fields": { "components": [ {{#each issue.customfield_XXXXX}} "{{this}}"{{#unless @last}},{{/unless}} {{/each}} ] } } Hi @Dd Please try this one :( 

Hi @PLaksh11 Happy to hear that!

Happy Holidays 🎊🥳

Hi, @Samed Torun Welcome to the Atlassian Community! This will work only for Company Managed projects; for Team-Managed ones, you can't use Epic Link. If your project is company-managed, try this Automation. Trigger: Scheduled -- > JQL--> project = "Product Development" AND "Epic Link" in (PD-544, CRBN-31, PD-374, PD-570,…

Hi @Saurav Kumar Singh Welcome to the Community! You can also try this one. assignee = EMPTY AND assignee WAS user.name

Hi @darshan_s1 You can use the REST API to do that. You can refer to this documentation for more information. https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-groups/#api-rest-api-3-group-user-post

Hi @PLaksh11 Welcome to the Community! Please inform, are Apple1,Appl2 Apple3, Orange1, Ornage2 and Orange3 separate custom fields or these are values for one customfield?

Hi @chihara Interesting thing. Will do some research to find out.

Hi @Trudy P Claspill I have done it through the Organizations. I provide access via the organization for the customers, and they are not receiving notifications. Thanks.

@chihara For the * AAA // ** BBB Try this one --> * AAA * BBB If you must separate them inline, use | or ; instead. For Color Tags. {color:red}Text{color} this works for inline text only. You can not use line breaks or special characters like // inside the color block. For the color try this one. {panel:bgColor=#FFEBE6}…

Hi @PLaksh11 Please try the following code, I am not sure it will work or not, but you can try. // Define field names mapping def mapping = [ 'A': ['A1', 'A2', 'A3'], 'B': ['B1', 'B2', 'B3'], 'C': ['C1', 'C2', 'C3'], 'D': ['D1', 'D2', 'D3'], 'E': ['E1', 'E2', 'E3'], 'F': ['F1', 'F2', 'F3'] ] // Reference the multi-select…

Hi @chihara Yes, Jira description is used to support a limited wiki-style markup. I think this will help you. https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all

Hi @Dejan Velevski { "fields": { "customfield_10201": { "id": "135" } } } Please try with this one.

Hi, @Trudy P Claspill Thanks for the answer. I know that from the Customer Notifications, it is being managed. But as I know, it is for all customers, yes? There is no possibility of making it visible to a specific group of customers, but they don't receive any notifications for issue updates.

Hey @Dejan Velevski Thanks for the answer. Please try the following one, I have missed "" characters. { "fields": { "customfield_10201": "135" } } You can change 135 with your Team ID.

{ "fields": { "components": [ {{#each issue.customfield_XXXXX}}"{{.}}"{{#unless @last}},{{/unless}}{{/each}} ] } } Hey @Dd Thanks for the feedback. Please try this one, I have added {{.}}, which is used when iterating over a list of strings instead of objects

@Dd Thanks for the feedback. Let's also try this one. { "fields": { "customfield_XXXXX": [ {{#each issue.components}}"{{name}}"{{#unless @last}}, {{/unless}}{{/each}} ] } }

Hi @Trevor de Souza The automation doesn't have time to update that field; that is why "Inherit Risk Test" is blank. Try to add the "Refetch issue data" action before the "Inherit Risk Test" field edit. I think, that should solve your issue. Thanks!

Hi @Nick Rally Welcome to the Community! It is because you are using a team-managed project. The Time tracking field isn’t available for validation rules in team-managed projects because it’s a Jira system field, and TMPs only support custom fields created within the project for validation workflows. For more control, use…

Hi @Lily Michelle Welcome to the community! It is used via the web version in a browser.

@Dd Thanks for the answer. { "fields": { "customfield_XXXXX": [ {{#each issue.components}} "{{name}}"{{#if @last}}{{else}},{{/if}} {{/each}} ] } } Kindly ask you also try this one.

Hi @Dd I saw that you faced an error during the parsing. Check the following one. { "fields": { "customfield_XXXXX": [ {{#each issue.components}} "{{name}}"{{#unless @last}},{{/unless}} {{/each}} ] } }

Hi @PLaksh11 Thanks for the answer. Yes, you are right, I have also reviewed and found out, that it is possible only in transition.

Hi @Dejan Velevski Thanks for the question. The Advanced Roadmaps Team Field requires ID, not name. The team field value must be a numeric ID. Try the following one. { "fields": { "customfield_10201": 135 } } Make sure to replace 135 with the actual ID of your team. Also, in the same rule, add Log Action; this will help…

Hi @PLaksh11 If you have ScriptRunner, you can achieve this by using Behaviours in ScriptRunner. If you have that: Go To: ScriptRunner --> Behaviours Create a new behavior and map it to your project + issuetype Add the following script. def field = getFieldByName("Your Multi-Select Field") def selectedValues =…

Hi @Allison Eglow Welcome to the community. It depends on which plugin you use. Can you provide the add-on name, as we need to check the documentation and find out which JQL searches they suggest.

Hi @Kyle Wilz Thanks for the questions. Your automation looks fine, except for the following points. For the flag edit action, you can use the following JSON in the advanced field. { "fields": { "flagged": { "value": "Impediment" } } } For the card color, Jira doesn't allow direct card color change via automation, but…

Ողջույն բոլորին :) @Anahit Sukiasyan ջան, մերսի շատ: Հիանալի նախաձեռնություն է!

Hi @Zaine Abaddin Thanks for the question. Let me try to explain it. You are right, Jira's permission model is nuanced, and what you are trying to achieve is not directly configurable through a simple property like jira.permission.comment.denied.group jira.permission.comment.denied.group = service-desk-users - This is not…