Why can't some tasks be set to in progress?

[Andy Watson]

I am using the greenhopper plugin with Jira and some of the tasks created cannot be set to inprogress. Some of them require the user to edit the task manually and set to in progress, other tasks don't even have that option.

The project is using the default workflow that has Open-in progress- resolved/done. I don't understand why this isn't working, it effectively renders greenhopper agile boards useless as you can really manage the tasks properly.

I am sure it is something simple, buti have no idea what it is it!

[Dobroslawa Wierzbicka · Accepted solution]

GreenHopper transitions are essentially your workflow transitions made graphic, so you'd need to look for a solution in your workflow:

- is there a transition from the Issues current status to In Progress?

- do some transitions have validators that would prevent some users from performing them?

- what Statuses are mapped to which columns in GreenHopper and therefore, what transition you're trying to perform by moving Issues between them?

[MattS]

The default JIRA workflow has a number of features that many people tend not to want. Not being able to edit closed issues, unexpected restrictions such as needing to have Permissions like Resolved and Close. I recommend creating workflows from scratch so that you know what's in them.

[Casper Oberleitner]

I had the same issue. In the Default Jira workflow one of the conditions for setting the status to "in Progress" was that it has to be assigned to you. That cleared things up for me. I think you can edit these conditions as well. I hope that helps!

[Andy Watson]

There is something odd about that specific users account. I cannot move his tasks into progress, i can move everyone elses and his account appears to be the same as everyone else. Its a member of all the same groups and has no more authority than anyone else.