so for assignee, will there be an option to assign to who ever transition the issue to a certain transition? We have been using previous assignee and does not work for all scenarios
Answer:
Ah, I do no think so…. I will have to investigate whether there is a way to do this. Feel free to raise this as a community, and we will have a think about it.
I noticed that this type of functionality is available in other tools such as Power Utils which is efficient. Not be able to assign to whoever transition is becoming an issue for us
Will Automation support retrieving/triggering and working with Project-level data? Like Project Name, Project Lead, Description?
This was answered live. You can watch the response in the recording.
can I access insight custom fields in automation rules and if yes, how do I access (syntax) attributes and multiple values?
Answer:
yes you do, insight fields behave as type "LIST" Check the documentation on smart values - lists
Can you explain how multiple condition statements work? For example, we create 5 subtasks. Then, if a field = XXX, create 3 more subtasks. You mentioned that as soon as one condition fails, the rule stops.
This was answered live. You can hear the response in the recording.
Is there a way to clone an issue into a project selected in a Project Picker field recorded in the source issue's custom fields?
Answer:
Yes, there is. When cloning an issue into a project, you can use a project id (selected from smart values, and therefore custom fields) to say which project to clone into
Should there be a need to write some code/scripts where do I do that ? Do we use groovy ?
Answer:
You can use Automation in combination with other tools, such as script runner, to do this. There are a lot of guides in community around doing this. Automation does not support scripts itself
Are there any plans to integrate Automation for Jira with Microsoft Power Automate to even further expand the automation potential?
Answer:
Not currently, but there is works to enable third party extensions for Automation for Jira
A request: It would be nice to set the actor dynamically. For example, the actor is the Reporter of the issue. Having to hard-code the actor is not always beneficial.
Answer:
Good request. For those who are unfamiliar with it, currently you can act as either the Automation bot, or the user who triggered the rule (which means either person who pushed the manual trigger/commenter on a comment)
How can I make the created ticket with the main ticket, i.e. create a linked ticket, filled in some of the fields
Answer:
You can set Linked Issues field. Update the field Linked Issues. You need to make sure that the rule actor has Link Issues permission. Also, make sure that Linked Issues field is on the right screen(s)
@Joanna Thurmann or @Sam Harding: I believe this is one we either didn't see or have time to get to…
If we want to see the recent created or updated rules, can you add a date column on the rules list?
Here is Sam's reply from ealier. "The label functionality is the only real way to manage/filter your rule list at the moment. There is no way to add the date of rule creation to the rule list. This is a good idea though, I will add this to our upcoming projects to work on for the team. Cheers!"
For more on automation, see this well-timed nice post from Rachel Wright: Jira Automation Ideas
This was also answered live. So, you can watch the response in the recording.