Hi everyone, please pardon any ambiguities or confusion since this is my first post and I am new to being a JIRA admin. I've created a custom workflow and attached it to a scheme that a project is referencing. When I go and create an Issue Type (in this example, a 'story' issue type) and try to start the workflow, I am getting an error with the following message:
The start of my workflow is here:
I get the exception when on the "Not Started" state trying to click "Start Development" to transition to the "Dev Started" state.
Any help would be greatly appreciated! Thanks!
|Not Started (1)||Not Started||Start Development (11)
>> Dev Started
|Dev Started (2)||Dev Started||Stop Development (21)
>> Not Started
Complete Development (51)
>> Dev Completed
|(Originating Steps)||(Destination Step)|
My apologies. Is this sufficient information? Please let me know if there is anything else. Again, I appreciate the help and quick response!
Ouch, that looks like a corrupted issue in the database. I see you've tried re-indexing, which is always worth a shot.
However, I'd run the integrity checker. This can correct entries in the database if they've been damaged.
If that helps, then it's worth thinking about the causes. In my experience, there are three main reasons
Hi, lunchbreak time, so I can attempt to give you some more things to check. Your post-functions looks good to me.
In the workflow designer
Here are some other things to check. When you click on "Not Started" and "Dev Started" it should highlight. Then click on the wheel(cog) to get the menu to display. Is "Issue Editable" checked? If not, make it so.
Now highlight the transition "Start Development" and then choose "View Conditions". You should see tabs across the top to show the conditions, validators and post functions. Do you have any conditions or validators set that could cause the operation to fail? If do not have a condition, then adding one.
Thanks for helping me out during your lunchbreak! I've checked all statuses and they are all "Issue Editable" except for "Closed" which we want to be in a final state. I also noticed that none of the transitions had any conditions so I added a "Assignee Only" condition to test. I've republished but am still getting the same error.
Do you have any other ideas? I greatly appreciate your help!
Hmm, By any chance are you using ORACLE as your database? It looked like MS Sql Server to me but just want to verify.
I would also try a group related condition if the issue was not already assigned.
I am assuming this is a new installation verses an upgrade, so please query(select) OS_HISTORYSTEP table to see what records exist in this table.
I've just received some word from Atlassian support when I opened up a ticket with them yesterday afternoon. I've sent them an XML backup of my database. I'll await their analysis and attempt to remove any duplicate entries. I'll update with the progress as soon as I can. Below is their response:
Thanks for contacting Atlassian Support!
Based on similar cases, I believe that the problem is caused by an inconsistency in the database. To be more accurate, with the <tt>os_historystep</tt> and <tt>os_historystep_prev</tt> tables.
There should be some duplicated entries on those tables and deleting those entries should be enough to fix the issue, however we can't confirm right now the implications of removing the data manually at the moment. With the XML backup will be possible to perform a deep analysis and provide an accurate solution for your problem.
We'll be waiting to hear from you on this case.
Yup, the integrity checker can find and fix these records when the data has slipped out of line, but it doesn't handle duplicates as far as I can remember. So finding and removing dupes is probably the way to do it, but very very carefully. I'm sure Atlassian will be able to tell you the best route.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs