About Jira and it's automation I will write much more other day. Now just a few words to introduce.
"Automation for Jira helps you extend and automate Jira - without the need for scripts. Think of it as Lego. You simply put the building blocks together and automate the processes you need easily."
The above quote is coming from the official Automation for Jira site. In my opinion the automation is not as simple as lego but yes it is very helpful and you can automate your processes with blocks building.
Alright let's move to the main topic for today. The issue was to prepare the automation rule for such thing: [When a new servicedesk inquiry is sent (issue is created) clone a task to other project with a "working title" (smart value) which should be copied from the servicedesk "summary".]
The main reason why I'm writing about this is that there is not way to do that without a one specific action.
Please analyze screen shots below:
When labels conditions are met this automation will edit an issue field and copy the summary to "working title". After that when an another labels conditions are met clone the task to the other project with the "working title" in it.
Looks simple but the above automation will not be possible without the action named "re-fetch".
Without it, automation will not copy the "working title" smart value and it will not be present in the cloned task.
The official definition of the "Re-fetch" issue data:
This action refreshes smart values with the latest field values. By default the {{issue}} reference is not updated during a rule execution, and therefore contains the same values as when the rule originally triggered.
It took me some time to figure it out why this automation did not copy this smart value named "working title". When I discovered it I wanted to shout it out.
Until next time, keep it up!
source: docs.automationforjira.com
No comments:
Post a Comment