I've noticed this now a couple of times recently in GreenHopper. Occasionally, I will come across an issue which I cannot transition from 'To-Do', to 'In-Progress', however I can move it directly to Resolved/Closed. I can confirm that I am the creator and assignee of the issue.
There are no conditions that I'm aware of that prevent me from moving the issue. I can create an identical issue (all the same details, points, assignee, etc) and move it directly to In-Progress.
Any ideas how I can track down what is going on? Is there any way I can do a diff on the raw data behind the issues (the one I can't move and the duplicate test issue that I can?)
Does the issue also can't be transit to In Progress if you are not in Agile ?
Does GreenHopper Simplified Workflow is being used ?
What are the statuses that is mapped to the To-Do and In-Progress ?
What are the Conditions and Validators applied to all the available transition ?
@Jack Graves [AC] first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this follow...
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