So generally we're working with project blueprints and only create projects with shared config. In some cases, the projects need individual configs, so we wrote a script in ScriptRunner to do that.
Everything beside workflow works fine. With workflows we have one bug. So generally we get the current workflow scheme and workflows, create a new scheme add new workflows and then assign it to the project. Then we migrate the issues via workflowManager.
The problem here is, that the workflow is assigned to the project, but is shown as inactive. Performing a restart of all pods, fixes this completely, but always restarting is not an good way to fix this.
Is there any way to activate the workflow via ScriptRunner? And how to migrate the "null" issue.
