We use Groovy ScriptRunner for Jira Cloud. Parent creation triggers a population of a template-based subtask family and dependency links. The Jira cloud add-in called Deviniti template population is also involved.
We need different "parents" created close together to receive their own complete task families, while preventing duplicate or delayed executions from creating the same parent’s tasks twice.
Please could someone with knowledge of Scriptrunner please advise on these specific questions:
- Exclusive processing: Does ScriptRunner for Jira Cloud provide a supported per-parent queue or locking mechanism covering listeners, continuation, duplicate events and recovery after timeouts? Please provide the applicable configuration/API if possible
- Conditional Jira property updates: Our draft uses PUT /rest/api/3/issue/properties/{propertyKey}, filtered by one entityIds value and hasProperty/currentValue. We have added asynchronous task-completion and exact state-readback checks. Does this operation guarantee that simultaneous claims against the same previous value cannot both succeed? If this requires Atlassian confirmation, please could someone help me with the appropriate escalation.
- Automatic continuation: The documentation I reviewed describes a ten-run listener self-trigger limit and hourly scheduled jobs with variable execution timing. What supported approach provides prompt continuation and recovery for larger task families without manual console runs?
- Task responses and permissions: Does ScriptRunner’s proxy expose the original 303 Location response or automatically follow it? Should the same Add-On User be able to retrieve the result through GET /rest/api/3/task/{id}?
- Native template hand-off: (This is more a Deviniti Template product question) What supported coordination approach should we use when Deviniti may still be populating subtasks, so that a ScriptRunner fallback cannot create duplicates?
Any assistance is warmly welcomed for this 🙏
Kind regards,
Kevin Dickson
