Hi
I have built an automation is triggered when a task is created. Part of the automation is to rename the Summary field based on the custom fields chosen.
Summary Field in Edit Issue
{{issue.fields.ROC Race Location.value}} - {{issue.fields.ROC Race Location.child.value}} : {{issue.customfield_10251}}
That all works and no issue.
What I would like try and do is add the created task to an existing epic.
I have a set of Existing Epics of locations, eg "Sydney Race Course" etc ... When the above automation is created and the location is = Sydney, I would like to move the Issue to the corresponding EPIC.
I assume this will be a JSON file type of rule where it would say if
issue.fields.ROC Race Location.child.value is equal to Sydney then move to EPIC called Sydney Race Course and so on.
Is any one able to help build the syntax, and then I should be able to adapt it.
Note that there are multiple locations that I would need to query.
Thank you in advance
Assuming you have defined set of epics.
For the created issue (Standard Issue Type), you want to link this issue to the epic.
So, within the same rule, you can add if/else condition
if location matches Sydney
Then add Edit Issue Condition, with following rule in
{
"fields": {
"parent": {
"key": "EPIC-123"
}
}
}
I am assuming there is no field in the issue being created to give you the actual issue key of the epic and hence suggesting a hard coded value of epic for each location.
Thank you for responding
I do apologies, I am struggling to understand what you are proposing. This is what I have put together
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the edit issue fields parent,
you need to provide a key to make the current issue child of epic.
So, you can add this under more options. replace EPIC-123 with your actual value
{
"fields": {
"parent": {
"key": "EPIC-123"
}
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.