Making Workflow backups with a space behind will crash Workflowschemes and project associations

As discussed in JSP-136266:

• make a draft WF from your current live-workflow, e.g. "Simple Workflow",
• when "do you want to make a backup was asked, I accidently hit space key followed by the pound/enter key.
  • This causes, there were TWO Workflows, one called "Simple Workflow" and another "Simple Workflow " (see the space key at the end.
• the second one was marked as "inactive" but marked as linked with the current live workflow scheme
• Then I entered the "backup" worflow and tried to rename it to "Simple Workflow - BU"
• This caused, the BACKUP was renamed but and WENT LIVE.
  • i.e. The edited and last live-Workflow is no longer associated with the workflow scheme!
• the "Simple Workflow" including the changes was now marked as inactive as like any other workflow backup
• Then I created a new Workflow Scheme, copied from current Live-Scheme and made use of the "Simple Workflow"
• Then I attached this new Scheme "Workflow Scheme v2" to a project
• All worked fine until ...
• restarting the server
• no issues of this project can't be opened anymore, just saying:

  Could not find workflow for issue 'PRJ-123'. This can be fixed by running the integrity checker

Indeed, it can't be fixed by integrity checker!

The "Simple Workflow" seems to get lost on restart!

This issue was "fixed" by:

• fixing the WF Scheme : https://confluence.atlassian.com/x/FQjCDQ
• creating a copy of the "Simple Workflow - BU" called "Simple Workflow"
  • This causes, any other relations in the systems are running again, and Workflow actions might be triggered.
  • IF this step is skipped, no transaction buttons are shown, nevertheless the integrity check says "all fine"

jtye

I tried reproducing this issue in my local instance (although I used JIRA 5.1), and I was able to reproduce it right until when you created a new workflow scheme which used the original workflow, and associated it with a certain project. Everything, from the creating of a workflow with a space behind, to the renaming of the backup workflow causing it to go live happened in my instance as well.

, I have not encountered the error where it says 'Could not find workflow for issue'. I am still trying to figure out what might have triggered it.