Jonny Carter Expert

I think this is a duplicate of your other question. Short answer: it's a boolean ( true or false ).

In answer to the bulleted list in the original question: Script post-functions get executed synchronously, in the order that they're listed on the postfunctions page. There's no concurrent execution, so sleeping won't help you delay until after other postfunctions have run. Per Jamie's answer on your other question, the…

So, one easy way to address the infinite issue creation would be to add a third clause to your condition that prevents cloned issues from being included. You could either specify the project & issue type that the target issue will be, then exclude that specific project/issue type combination in your condition. Another way…

Initializer scripts are always run as soon as the page is loaded, and are only run once. If that field is empty when the page is run, you should expect its value to be null when the initializer runs. If you need a script to run every time a particular field changes, then it needs to be associated with that field. For some…

You can use Behaviours to modify the visible/required fields on a screen. You can use a scripted transition to limit the behaviour to a particular workflow step, so that it's only applied on the relevant transition screen. You could add an initialization script to a behaviour with something like if (getActionName() ==…

Hi, Anupam. So, there's a lot of layers to what you're after. I think I can get you over the immediate road blocks, though. * Why are the sub-tasks staying in the "Open" state? The answer, based on the screenshot you provided of your workflow, is that to get to the point where the subtasks have a step leading to "Approved"…

It could prove helpful, yeah. Another thing to test is whether other methods of sending emails outside of ScriptRunner send multiple messages as well. If so, then it may be an issue with your Mail Server settings in JIRA itself, not the post function.

Think you could share your listener's configuration and the configuration of your workflow? If the listener is only firing once, it could be that the same email address is getting included multiple times via the To Addresses, To Issue Fields, CC fields, etc.

I assume you're using the Send custom email post function in one of your workflows. Several questions to help debug this: * Are the emails the users are receiving identical? Or are there differences between them. * Do multiple workflow transitions have this step? If so, it may be that users are getting the emails because…

Here's the same script, with imports and more relaxed typing: import com.atlassian.jira.component.ComponentAccessordef customFieldManager = ComponentAccessor.getCustomFieldManager()def approvalNeeded = customFieldManager.getCustomFieldObjectByName("Approval Needed")def value = issue.getCustomFieldValue(approvalNeeded) See…