Population of Description from other projects

[Dmitry Alabyan]

Greetings, Community!
I want to set up an automation between the two projects, where filling fields on one, triggers task creation in the other (that I did easily).
What I am interested in is - whether you can dynamically populate the description based on the fileds?
E.g. when the trigger issue has filled fields X Y and Z AND triggers a creation of a task in the other project - can the Description field in the newly created task fetch the values of the X Y Z inside?
Perhaps that can be somehow coded for the field within automation?

[Tom Lister · Accepted solution]

HI @Dmitry Alabyan 

When you create the new issue you can use a mixture of text and smart values to create a description based on the data in the triggering issue.

See this link for available smart values and usage

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

[Dmitry Alabyan]

Exactly. What I am searching for is what smart values would be applicable to populate the end issue description based on the field in the trigger issue.

[Tom Lister]

What issue fields do you want to use in your description?

[Dmitry Alabyan]

These ones. I have a dossier project with all the data, while the result of the triggering are Invoicetasks, that need the description to include all these numerics

[Tom Lister]

Hi @Dmitry Alabyan 

As custom fields you should be able to access with the syntax described for Custom fields in the docs

e.g.

Mediabudget Brutto :   {{issue.Mediabudget Brutto}}

To test what  what a smart value returns, use the Manual trigger with Log action.

[Dmitry Alabyan]

it will the fetch the field value of the newly created issue. I am looking more for the syntax to fetch from trigger to the new one.
plus, I have commonly encountered (when trying to implement auto-calculations via smart values that ira doesn't recognize or distinct the names of the fields somehow from time to time. So it returns empty values or fails
Do you know if such practices?

[Tom Lister]

HI @Dmitry Alabyan 

to access to triggering issue try

{{triggerIssue}}

Refers to the original issue that triggered the rule;

If you have problems access via field names try the field id syntax. Field names can change and be duplicated. The internal id's stay the same.

{{issue.customfield_10099}}

There is a note on finding the smart values in an issue here

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Using Manual triggers to run and log output is the best way I've found to test formatting issues.

[Dmitry Alabyan]

@Tom Lister thanks for the insights, the syntax approach helped a lot.

might you also know how to specify the fields in specific subtasks also?
Here: i have numeric fields in the subtasks of an issue, that I need to sum up in the parent. But that is needed only for the subtsks with a specific prefix in the Sumary.
hence, the regular {{issue.subtasks.field.sum}} doesn't apply

[Tom Lister]

Hi @Dmitry Alabyan 

I don't know of any inbuilt way to do conditional summing.

Is it possible in automation to loop through sub tasks using a branch rule 'For Sub Tasks'. You can add tests for summary in the loop.
I'm not sure how you would add the values to the parent in steps.