Hello All,
I have custom field (Customer) on Initiative level and want to automate that once this field is updated the Customer information should be filled on Epic level as well.
Seeking help on it
Hi @Arvind
If I understand you correctly, the initiative is above the epic and connected by the "Parent Link". You want to make it so that when the Customer field is updated on the initiative level, you push down the updates to the epic level.
This is possible with Automation.
1. When: Value changes for "Customer"
2. If issuetype = initiative
3. For: choose JQL
4. Then: Edit issue fields and use the smart value {{triggerIssue.xxxxxx}} - replace the xx's with the custom id for the field you want to update.
Please let me know if this works for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In part 3, you will want to use this JQL:
"Parent Link" = {{issue.key}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Arvind
Happy to look, can you provide a screenshot of your automation and explain what is not happening?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So the automation you have there is quite different the the one i recommended. Can you try this one and see if it works for you?
Notable differences:
- No need for the lookup, my JQL is just to ensure the change is an initiative issue type.
- Since the issue type is not epic, the For: Stories may encounter problems, so i recommend a simple For JQL and look for the parent key.
Here is a screenshot to help:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It works for me. Interesting.
Two possibilities on the top of my mind. Can you show me the details of the "edit issue" component? Also can you show the audit log with its details expanded?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Edit: copy and pasted the wrong string. Updated with the right string
Thank you for the screenshots. So you've covered up one of the pieces I really wanted to see. In the edit issue, in that set box that you're drop down is covering up, are you using this string:
{{triggerissue.customfield_10000}}
Replace the XXX with the ID for the custom field
If not, give it a try.
The trigger is working and it is updating LCE-29, I assume this is the correct issue it's supposed to be updating. If so that means the only problem is it's not updating the right field or using the right data to update. Which means we've narrowed down the problem to that edit component.
If it's not supposed to be updating LCE-29, then we need to look at other components.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you don't know the custom ID, then open up your custom fields in the settings and go to the customer custom field and click edit. You'll find the ID in the URL. It will be the last five numbers in the URL. Use those numbers to replace the 10000 in the smart value below.
The format you should use is
{{Triggerissue.customfield_10000}}
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.
Hey @Ben Finn ,
Again seeking your expert advice.
I wanted to auto create Epic->User Stories->Tasks while creating new Initiative. which is working fine.
How i can automate the rule which can help me to auto link as below while creating these structure. i.e Initiative will be my Parent link and User story/Task will be child to Epic
Initiative->epic->User story->Task
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.