Vishal Biyani Expert

@AndraskoP When you are importing in second project, can you share the SS of the import file that you are using? Also, can you share the logs (if any) once the import issue is done? Below is the caveat as noted in the article, 

it should be like this {{#debug}} {{ ClosingCategory.get(issue.customfield_19832) }} {{/}}

@Wojciech Szczygłowski I wrote this quick automation to test. It is working fine at my end Do note that as far as i Understand you can't have a subtask in one project and parent task in another project. Epic can be in another project while StandardIssueType can be in another project

Table is fine. Check and share what you have in RootCause? it should be using the lookup table

@Wojciech Szczygłowski Can you share screenshot of the automation that you have written so far? if you have not written anything so far, I suggest you take a first stab at it. * Start with a Trigger for Issue transitioned * Check if the issue is of subtask type * Branch to Parent * update the status.

@Mansi.Gusain In Query Params, add a variable fields and value as the relevant field that you need e.g. summary, priority etc

@shankara vijayendran This should get you going. Create an automation, with a scheduled trigger. Trigger In the trigger specify JQL project = "TEST" and attachments IS NOT EMPTY Uncheck below checkbox This will return list of issues that have attachment. Then add Conditions For demo purpose i just added a log statement to…

Log shows you are getting Cutover as the value, so you are not using lookup table, while creating the RootCause variable. Can you revisit your rule.

if you run the below JQL, it will give list of issues that have attachments attachments IS NOT EMPTY Then, you can loop through each issue key, using REST APIs, to find issues that have size > X. Are you looking for other option like automation?

@shankara vijayendran if you are open to use REST API, then one of the endpoints that can be used is url = "<a href="https://your-domain.atlassian.net/rest/api/3/attachment/%7Bid" target="_blank" rel="nofollow noopener noreferrer">https://your-domain.atlassian.net/rest/api/3/attachment/{id</a>}" You can read through the…

@Karolina Yeong In the edit issue field, you can use copy Teans from parent. You may not need to branch to parent as long as it is ensured parent has Teams field populated

Add one more } at the end. {{#debug}} {{ ClosingCategory.get(issue.Helper Issue Creation) }} {{/}}

So wherever smart values are being created, enclose them in {{#debug}} {{/} for example, for RootCause {{#debug}} {{ ClosingCategory.get(issue.Helper Issue Creation) }} {{/} When automation is executed and value is not getting set you know the problem BTW, WHY are you using Helper Issue Creation, you need to give your…

@Mohamed Eid Were u able to check?

Looks like Root Cause variable is not getting value. Add more log statements to check where the conditions are failing and go from there.

@Martin Karlsson Can you try with {{issue.fixVersions.name}}? To iterated through each version something like this is required {{#issue.fixVersions}} * Fix version: {{name}}, released on {{releaseDate}} {{/}}

This is good progress. Can you expand the audit logs to understand where the issue is not meeting the condition? Do validate that your case matches. Otherwise, string comparison may not work and hence field is not getting set.

@Pasi Pönkkö While branching, instead of using Children, use Advanced branching and set it like this Now you have access to individual items. If your response is JSON, then you can use dot notation. if it is a string then you will need to compare based on the string condition you were trying above. Would be interested to…

So you need to execute this transition on a bug that has Status Fixed to Closed. then only automation will get triggered. The bug SS that you shared is already in Done status. So in this case the automation will not get triggered

can you share the trigger for your rule?

@Pasi Pönkkö i am not clear why you are using webhook. see if you create a rule like this, does that serve your purpose?

in the rule you have missed starting and ending curly braces

Can you share the audit log to understand where the rule is not hitting? Audit log is right besides Rule Details

@bert.vogel Can you try clearing your browser cache and see if it works?

Good to know that it finally worked!!! 

@[deleted] are you referring to this link https://jira.atlassian.com/browse/JRASERVER-78353?

in my audit log, this is working fine. Can you check if this automation getting triggered from another automation? The message that you are getting, there is no checkbox anywhere to give this message :-( No related issues that have been updated since the last time this rule executed could be found. To include all issues,…

@Nguyen Thanh Tien Saving the last comment from Epic in a smart variable and then using that smart variable to update the comments is working Can you try?

@Nguyen Thanh Tien This is how the rule should look

try adding re-fetch issue data after the check for Issue Type equals Epic