we're using Jira 4.3 with Greenhopper 5.6.5.
Is it possible to disable the ability to log work on issue type base? i.e. It should be possible to log work for, lets say for the issue types "User Story", "Task", "Error" but not for the issue type "epic".
Important: Is it possible only with the build-in time-tracking of Jira? (without any of the existing commercial plugins like tempo etc.)
I tried to remove timetracking field from screen, but still everybody who's allowed to log work can log work.
Old question, but an easy solution exists for this. Assuming you have an existing Workflow for just the Epic issue type, simply add this Property Key to each of the transitions in that Workflow. Leave the Property Value empty. Be sure to publish the workflow after creating the draft.
Thanks for the info. Paul - I found that adding the jira.permission.work.denied to each workflow Step Name (id) --> Properties, was the solution here, rather than the workflow transition (within the On-Demand version).
Maybe this has changed since the solution above was provided as some time ago. Thanks for pointing in right direction however
This is not working any longer for me either.
I am trying to control which Issue Types can log time.
I have build two workflows, one for stories, epics and tasks which deny time tracking using jira.permission.work.denied and one for sub-tasks and bugs which allows time tracking.
The differences in permission on the two work flows have no effect. All issue types are still able tot track time.
However, if I add "All Unassigned Issue Types" to the workflow which disables time tracking, time tracking is removed for ALL issue types.
It appears the mapping of "All Unassigned Issue Types" is overriding the permissions assignment of specific issue types.
I have tried assigning "All Unassigned Issue Types" to its own workflow which allows time tracking whilst leaving specific issues in the "with time tracking" and "without time tracking" workflows but jira.permission.work.denied is still ignored.
If you're on Cloud like me there is an outstanding bug that causes this property to be ignored in certain cases. We're still waiting for a fix. I can't even remember all of the details, but overall, workflows with certain properties (this one included) on them aren't being honored.
Not really. Permissions are done at a project level, not issue type, so the "can log work" permissions follow that and can't be done on a per-issue bases.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
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