I remain very very disappointed with Atlassian. But how do you keep such an important feature like auto refresh of the page after the action of an automation rule, stuck in "request of interest" since 2018 !!!!!???? Does anyone happen to know an alternative method to force a custom field to refresh after making an automation rule?
https://jira.atlassian.com/browse/JRASERVER-67582
This is sort of possible I've found with some triggers.
On Triggers such as...
You can open the More options section and check Execute this rule immediately when the rule is triggered, instead of in the background
This means instead of waiting until the page refresh, the actions are included in the triggering action (eg. editing an issue) - and thus an inline edit will include the automated actions also.
Do take note of the warning though when enabling this...
Enabling this option means that an issue operation performed by a user (e.g. edit issue) will not complete until all automation rules triggered by the issue event have finished executing. Results of the rule executions will be shown immediately.
This can cause performance problems for Jira depending on the number of rules listening for events, and depending on how many issue events get triggered concurrently. If in doubt, please leave this option turned off!
Please note that rules triggered by 'Issue created' or 'Issue transitioned' and containing a 'Transition action' cannot be executed immediately. This is due to limitations with Jira's workflow engine. See JRASERVER-40597 for more details.
Let us know if this resolves your query!
Ste
@Ste Wright thanks for your help and your comment, I will try it so.
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.