Sherry Goyal Atlassian Team

Hello @Zac Wolff If you want to log work always against a fixed user 'Zac Wolff', then set the actor to 'Zac Wolff'. See this for help. Automation does not have the capability to log work on behalf of someone else like the issue creator, reporter, etc. We have improvement logged here. At the max, to dynamically set the…

@pedro_pizarro_bip As I already mentioned above, the field value change trigger does not work as expected on "log work" and "timetracking" fields the way you are using in the above screenshot(Sorry about that). Here is the ticket where we are tracking it: https://codebarrel.atlassian.net/browse/AUT-1648 Meanwhile, you can…

@Tomas Penka Hi! The field value change trigger does not work anymore now(Sorry about that). Here is the ticket where we are tracking it: https://codebarrel.atlassian.net/browse/AUT-1648 Meanwhile, you can try using the work logged trigger - there is a workaround mentioned…

Hi, The rule can be like this: Trigger: Issue created If User Condition choose "Worker A" field from dropdown(if its of user type) Issue filed condition: Assignee from the dropdown "is empty" then: Assign issue to {{issue.customfield_1234}} // customfield_1234 being id of Worker A field else User Condition choose "Worker…

Hi, Here is the document to help debug the rule. Hope this helps! Thanks Sherry

Hello @Виктор Бровков I am Sherry, a backend engineer on the Automation team. Thanks for reporting this. I have added a ticket to our backlog to fix this. I don't really have ETA on when this will be fixed you can check the updates on this ticket. Thanks Sherry

Hello @Jean Francois Gelinas Can you try using "Re-fetch issue data" action before your if condition and see how it goes? Looks like you need to re-fetch the issue to read the value you set via rule. Aso try logging {{issue.poeperties.ruleexecuted}} by using "Log action" before if condition to see if this value was picked…

Hi @Guy Mandel Can you try printing its value to audit logs and see what comes in there. {{issue.customfield_10104.value}}, {{issue.customfield_10104.child.value}} If these values comes out to be empty, try printing this: {{issue.fields.customfield_10104.value}}, {{issue.fields.customfield_10104.child.value}} Either one of…

Looks like this question is asked before in community and folks checked with support, they said they will visit the decision but no fixed deadline yet. Ref: https://community.atlassian.com/t5/Jira-Software-questions/When-are-the-workflow-triggers-for-branches-going-to-deprecate/qaq-p/1611693

Glad to hear that. Thanks for the update. This work in is progress to put together these docs but yes I will update our technical writer with your feedback. Thanks!

For updating Insight fields, might be good to try this: https://documentation.mindville.com/display/ICV53/Insight+with+JIRA+REST-API Let me know how it goes!

Hello @Mateusz Janus We don't support DVCS for devops automations. Jira DVCS connector can sync information between self-hosted Gitlab instance and Jira cloud(like you have already achieved) but doesn't work with devops triggers. This is the doc that talks about various ways to configure development tools for devops…

Hello, Of the top of my head, you can try using: Trigger as Incoming webhook which can be triggered from MS side and then use Send Web request as action to call your rest api. Give that a go and see if that's what you are after. Cheers Sherry

Hello @Mustafa Slatewalla Thanks for writing to us. This is not possible at the moment but we are tracking it under ticket AUT-29 and AUT-396 Sorry about that. Cheers Sherry

Hello Your schema type is "any" not "array", hence you are facing this issue. Might wanna try re-creating custom field of type array and this shall work then. Sherry

Hello New automation doesn't looks at html tags or ids. It will only look into actual description field content to apply operators. You can read more on conditions here. Cheers Sherry

Hello @Miguel Blasco Documentation is present here. I would suggest to make some GET API calls to validate structure of object, allowed values and possible operations. Look for more details here. Hope this helps to debug your case here. Cheers Sherry

Hi @Sunny Can you please tell if its server or cloud? Also, please share snapshots(rule and audit logs) in order to be able to give better advice on this. Also, will be good if you can do a quick test using manual trigger rule to test "Send email" action. Thanks Sherry

Hello @Jeffrey Bistrong Thanks for reaching us. I am sorry this is not possible at the moment but we are tracking it under: AUT-617 Looks like there are some complications to be able to enable this. Sorry about that. Thanks Sherry

@Виктория Issue field in "Link issue" action is type-able(which looks like dropdown). I think that's causing confusion. You can put exact issue key here, select appropriate option here or use smart value here like @Alexander Pappert pointed. Hope that helps! Cheers Sherry

Is this server or cloud? In cloud, I verified behaviour of branch execution is as expected and inline with the document. Thanks! Update: We have raised ticket in backlog: https://codebarrel.atlassian.net/browse/CAVE-3429 to correct document! Document states that if a branch only has one issue it will be run inline.…

Hello, This rule worked just fine for me for both the cases - when moving across the board or doing it by myself: Thanks!

Hello, For first part of the question, to be able to pull up a parent ticket, I would say try refining JQL a bit. See if this helps. For this part of question: I want the tickets that show up to the clients only be tickets that belong to them and not other clients as well. We do have an improvement ticket in our backlog.…

@[deleted] https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Create-variable-New-component/ba-p/1448118

Hi @Dan H Thought this would work by using "Field value change" with "parent link" field but no luck(for non next gen). I have taken it as a bug. Thanks for the feedback. Thanks Sherry

Hello! If under the hood, Xray is using jira custom fields then probably automation might help. If not, then there is no integration of automation with this. I would suggest to reach out through support portal, so that somebody can take a closer look and see if its doable or not. Thanks Sherry

Hello @Julia I suppose, your branch condition is always returning false hence your rule exits before executing the action. You can check audit logs and verify this. If you are working on issue types for which parent -> child relationship hold true, you can use "For parent" type directly, for example this. Hope this helps!…

Hello @chrisb , I do have a way to suggest. Use this smart value {{initiator}} which tells user who triggered this event and use it with User Condition. Hope this help! Cheers Sherry

@NicolasRiquelme Di you try clubbing branch on "most recently created issue" and manage watcher action. Try something like this: Let me know how this goes. Good luck! Cheers Sherry

Hello @robert Mugabuhamye We fixed it in cloud. Sorry I am not aware of the server.