I slightly modified a workflow copied from the Default (basically removing Resolved step and all pointers to/from it which I'm using for Tasks alone).
Now I'm trying to work in another modification, that being a "Blocked" status. So far, my mapping looks flawless, but I get an odd error ONLY when I put the issue into Closed, then Reopen it, then move it to my new Blocked column. (I'm doing all these transitions in my GH agile board, btw).
Though I have a transition from both the Open and Reopened state to Blocked and from Blocked back to Open, I get this error:
"It seems that you have tried to perform a workflow operation (Reopen Issue) that is not valid for the current state of this issue (Reopened). The likely cause is that somebody has changed the issue recently, please look at the issue history for details.Please refresh the issue and try again."
It tells me that when I'm taking a reopened issue and putting it Blocked!
See my text view workflow attached.
I just updated your support ticket but wanted to make sure I included this here as well -
I think if you're moving things around a lot in a short period of time, you might want to do a re-index (or give it a few minutes), or just ignore that message as long as it seems to be completing the transition.
Thanks Dave. I'll check it out, and in the meantime call this case closed, but to me, this still seems a bug with Greenhopper in specific. I say that just because when I transition quickly in full Jira view of a ticket, no errors are thrown. I understand under the hood, it may be indexing, but only Greenhopper gets confused and displays an issue. Up to you all if you want to fix it, but for me, I'm going to ignore this now unless or until it becomes a problem in real-world use. Thanks for your help.
also, i just tried to wait and did so once for over 10 minutes to find it didn't prevent the GH error.
i've found that for some reason, the ticket MUST go to Closed > Reopened, and then the error shows. waiting over ten minutes didn't prevent it, so i'm not fully certain waiting an hour or more (in real world) will be any different.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot