Re: Limit the ability to change the Due Date in JIRA to a specific group

That all looks correct, so you'll need to go back over a couple of things really carefully.  The screenshots are very clear that you've got most of it right, but there's two things to check
# Check that you are in the C&E Leads project role - Jira hides the transition completely if you don't have the rights to it, so it may be as simple as you not actually being set up correctly!  You can check this another way - try creating a draft of the workflow and remove all conditions from the "edit due date" on "open" so that anyone can use it.  If it still doesn't appear on issues in the open status, then you know you aren't using the right workflow, and you need to check over the workflow scheme!
# You don't mention screen-schemes anywhere.  These are the things that determine what screens are used for the Create, Edit and View actions (outside the workflow).  You should drill down these to make sure your project really is using the C&E Edit screen (without due date!) for Edit actions

Another two quick points, which aren't related to the problem you're looking at now, but I spotted:
# Check your edit transitions - I didn't see them saying "screen to use = C&E due date edit".  Without the screen, the transition will just go "ok, done", appear in the history, but not actually allow any changes.
# In 2.jpg, you might want to check the end-points of "edit due date", because they don't all loop back to the same status.  That may well be intentional of course, I can understand where replanning and changing the date would be a good thing to have it change status as well, but I thought I'd mention it.
--
Post by broughn2 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=55274
_______________________________________________
Jira-user mailing list
[email protected]
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user