Can anyone of you please let me know, how to make my {{issue.key}} or {{issue.summary}} as hyperlinks while adding in rules to access that issue from slack?
Hi @John McKiernan! Automation is making our lives a lot easier :) Thanks for rolling this out!
I created an automation to sum Remaining Estimate of all subtasks and update the parent ticket's Remaining Estimate each time a subtask's Time Tracking is updated.
Automation ran but the result is off
Parent A has 2 subtasks (Subtask X with RE of 2h and Subtask Y with RE of 1h)
Automation updated Parent A's Remaining Estimate to 10,740h (360w) instead of 3h.
Here's the smart value syntax {{issue.subtasks.Remaining Estimate.sum}}
thank you so much for the webinar and the article, it really is making life easier. I wanted to utilize the automation in example 1 as it is one we would love to use. I have set it up as is shown in the example. The rule runs, but it keeps giving me the status of no action taken with the reason: Issue condition not met.
I created a new epic, so I am a little confused as to which condition was not met. Do you have any ideas what might be causing this? We are using JIRA Cloud.
Hi @John Funk - wow that was fast! :) Hello. Screenshot is included below. Bascially it's the German version of the English example. The test Issue JIRA-32 was created as an epic. As you can see I have tried a lot to get it to work with no luck....
Is this a Next-gen project? Because I know there are some issues with Automation for Jira and Epics for Next-gen.
Maybe as a test, change the rule to another issue type (like Task or Story) and create one of those and see if the sub-tasks get created. If so, then we know the Epic type is suspect.
as usual @John Funk is quicker than me and on the mark!
Actually, I think I know what happened here. It's possible that if this rule was created at a Global level, the "Epic" or issue-type that was chosen here isn't a global issue type (This is pretty much the last piece of the puzzle that we need to fix to make Next-gen and automation work flawlessly together).
Or if the rule was created in a specific project that later was switched to a global rule, the issue type wouldn't have been a global issue type either. Essentially, if this is true, it is the unfortunate effects of this bug which we are working on fixing:https://codebarrel.atlassian.net/browse/AUT-1936
As John mentioned, if you switch out the epic for a task, it should work thus proving this.
@John Funk yes, we use projects of the next generation.
@John McKiernan I have tested it with different issue types, it seems the problem doesn't only affect the epic type, but also task types, I couldn't get it to work with either.
Thank you for letting me know about the bug. :) I was getting worried that there was something I may have missed.
I tinkered with the rules a bit and have copied the automation rule to a test project and tried to run it there. I finally managed to get it to run successfully and create the sub tasks automatically and link them up to the epic that caused their creation. Another road block was initially not having a text in the description which caused an error in the rule as the field could not be removed and caused the rule to fail. With a text in the comment field the rule runs like a charm.
Now to copy the rule to the other projects. :) I will still have to figure out how to best move the issues from the backlog to the board in next gen projects without scrum. I know about issue JSWCLOUD-17471 and will keep an eye on that. Till then I have to find a best practise.
Hi Tina - glad you got it working! Thanks for the good feedback and screenshots. And thanks as always to @John McKiernan for jumping into the fray. :-)
40 comments