Phong Nguyen - Atlassian Solutions Engineer Insider

Thanks, everyone, for your valuable feedback and additional insights! I really appreciate Jens's suggestion of "Cloud Updates for Atlassian site" – that's another great resource for the community. Brita, I'm glad you found the checklist solid and that previewing features in a sandbox works well for you Rune and Dave, I…

Great feature! Btw it should be nicer if we can not only use variables "pass from the intent flow"but also "pass variables from the automation result back to the intent flow", we can't ensure the automation execution is successful or not, and we might need some response data from the automation like the created ticket…

I'm facing the same issue, it seems like the lines only show when we use Group by "None". I tried to use Group by Team or Project, the lines doesn't show up for both cases.

What a great improvement! By the way, for anyone using the smart value to access global fields via automation ({{customfield_id}} or {{customfield_name}}), we nee to add those global fields to this team-managed project setting section unless the smart value will return an empty value.

*Deleted*

@Sam Knight @Hanh Pho Could you please provide more clarification about this related post? https://community.developer.atlassian.com/t/removing-access-to-forms-data-using-jira-entity-properties-api/80912 We’ll soon be removing access to Forms (previously ProForma) data currently stored in entity properties from both Issue…

@Jitendra Singh I believe we can only configure SSO for Bitbucket Cloud with the Atlassian account and very limited user provisioning features (NOT including group sync). It's mentioned in this link: https://support.atlassian.com/provisioning-users/docs/configure-user-provisioning-with-okta/ Provisioning is available for…

Hey @刘柏榕 Baron Liu (ENG - IT - CN) Can you check if your scheduled trigger includes any JQL? For this approach to work as expected, the scheduled trigger should NOT use any JQL. I think your scheduled trigger also includes the same JQL of the lookupIssues, so it multiplies the loops. If you still can't find the root cause,…

You should use Log action in the automation to check each {{approverEmail}} item in the loop to see if it's duplicated. Sometimes, it might be caused by you creating 2 of the same automation rules but you forgot to disable one of them.

Hey @刘柏榕 Baron Liu (ENG - IT - CN) , did you use the distinct function in step #4? {{listApproverEmails.split(",").distinct}}

@Nguyễn Thành Long hey bro, did you try to log/print the {{approverEmail}} to see its value inside the loop?

If anyone is interested, I created a Jira automation approach here to handle this case: https://community.atlassian.com/t5/Jira-discussions/How-to-remind-all-approvers-by-Slack-that-have-pending-approval/td-p/2390360

Hey Kiet, just wanted to drop a line to say how awesome that diagram you sent me was! Seriously, it's amazing, and I'm so grateful to have seen it. Thanks a bunch!

UPDATE: You no longer need this workaround since Atlassian has fixed the bug.

Thank you @Hong Quyen I can find the Directory ID from the Identity Provider portal (Okta for my case). Thank you anyway.

Hi @Hong Quyen Are you able to get the Directory ID or the domain ID to make it work? I tried with the domain ID but it does not work.

Hi @Konstantin Gagač The previous function that I mentioned works fine via the Inteliji IDE (Java JDK 8) but somehow doesn't work with Jira: Anyway, I retested in the Jira Automation and found this correct one: {{Description.replace("\\n", "")}} (Note: Kindly notice that it should be "\\n" with double "\\") Test result:

Hi @kon Can you clarify your case further? are you cloning an issue and the content "lorem p\n ipsum" is from the summary of the source issue?

@Xavier did you try outboundReferences() instead? You should try the hardcoded value first to validate the IQL syntax inside the Insights schema: 

I have an alternative solution for this, not ideal but might help. 1. After the issue is created, we can access the Forms field data based on its properties, fox example: For the ID of the field: {{issue.properties."proforma.forms.i1".design.questions.1.choices.get(0).id}} For the label of the field (display value):…

I have a solution for this: use {{issue.summary.replaceAll("\n", "")}} to remove all newline characters ("\n") instead of {{issue.summary}}.