We have the following issue: our project has a Default Assignee option set to 'Project Lead' (or to Component Leads, but even without components I see the same problem).
And then for some issue types (sub-tasks, for example), we would like to remove Assignee.
I put 'Clear Field Value' post-function for the Create transition and clear the Assignee field there. But it just does nothing. Any new issue is always assigned to the project lead after creation.
I have tried to change the position of the post-function, even putting it as the latest in the list. No results.
Does anybody know why? I have found one way to fix it with Automation, but I would like to do it without any Automation rules.
If you have an app, like JMWE, you can use a PF with a delay of e.g. 500ms. This means that the PF will run after Jira finishes with its automations. Jira automation used to be an app, and the automation rules run after the native automations. That's why your solution it's working with Jira Automation.
Thanks, @Alex Koxaras
I expected something like this for Automation rules. But it is interesting why the PF doesn't work in this situation as I expect that the following 'Creates the issue originally' should be finished (including the default assign) BEFORE the next PF is executed.
It doesn't work because it run async. If that was going to work, I would place the PF after the "FIre Issue Created" event:
Try that and let me know if that works. :/
Another solution would be to:
So basically what you do is, after the on create transition and after Jira has placed the default assignee, you call another transition (while staying on the same status) which clears out the assignee.
Hope the above helps!
Yeah.. it seems that there is no native PF for transitioning an issue. You could always use automation to transition the issue :/
JMWE, JWT, scriptrunner, JSU all of these apps have these PFs. You can always install one and try it out and if you don't like it, unistall it without charge.