I have a basic question on transitioning permissions...
I've just setup a test with a Greenhopper Kanban board - in work mode, for unassigned tasks I can drag them to the 'resolved' and 'closed' status columns but not the 'in progress' one. If I assign the task to myself first it allows me to drag to 'in progress'.
If this is by design, I would expect GH to stop a user closing an issue that wasn't assigned to them too?
So far I am still using the standard workflows and there are no special security schemes setup, can someone please point me in the right direction?
No, you just need to edit the condition(s) on the "close" and "resolve" transitions, OR change the permission schemes.
The transitions will have something like "user must have resolve permission" on them, so by editing the permission scheme, you can determine who gets the permission. Or change the workflow conditions.
It was unclear what was causing that behaviour - certainly for a newbie getting used to the system! Not sure how you would get around that, maybe display a hint/tip when you drag an issue? I understand why it happened now, I copied the standard Jira workflow so my new workflow inherited all the conditions from that.
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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