I've been asked to set up a state that will prevent users from logging work on specific issues in a project, despite the fact that they will have permission to log work on other issues.
The scenario is quite specific to our internal process, but it would be similar to a professional services company having a "Customer has been billed" status on an issue where any further hours cannot be logged. This is a contrived example so please forgive the flaws :)
Can I set it up such that an issue status prevents time logging? It seems something simple enough that an option may already exist, but I cannot find the right switch.
Sorry to resurrect this but I want to keep a history of my issue alongside your solution.
I have changed the Closed Step Property to jira.permission.work.denied / denied and it seems to do the trick!
However, it looks like the Transition Screen (to Resolve/Close issue) is no longer accepting the log work input. So, the Log Work field appears, I enter time, but the time is not saved (no error takes place, not even in the Atlassian logs!)
Looking into the Transition Post Functions, I see this in the following order (and according to Atlassian, these can't be reordered)
So, I see what the issue is (the first step in the transition is to set the status to Closed, so no further work can be logged against), but I can't find the workaround! Can you help?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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