Workflow is inactive, but assigned until restart

[Nico]

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.

[Carla Ann K_ Rowland]

I would double check the api and see which field holds that inactive flag. if it is not readily documented I would open a ticket with Atlassian to help identify it especially if it is not update the the status is not cascading as it should..  Here is a starting point if you haven't already access this documentation: https://developer.atlassian.com/server/jira/platform/rest/v10004/api-group-workflow/#api-group-workflow

[Carla Ann K_ Rowland]

If the workflow is included in the workflow scheme and the scheme is attached to the project it should become active when the issue types are assigned to it. It should not require a restart. 

[Nico]

yeah this should be the case, but it isn't.. the workflow is assigned and works, but it is marked as inactive, too at the same time..

So when I go to project settings -> workflows and then press the edit pencil i'm redirected to the global admin interface and only in this interface it says "inactive" "used in 1 project", also in the global administration it's at the bottom in the inactive tab, but it's added to a workflow scheme and this scheme is added to a project, but only a restart fixes this...

even the blocking indexing does not help..