Currently a user can log work under an Epic, Issue and Sub-Task. Is there any way to prevent (disable) them from logging work under the Epic while allowing them to log work under the Issue and Sub-Task?
Thanks!
Tudor
Tudor - This is very easily solved. 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.
jira.permission.work.denied
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How can I define a workflow just for an epic (JIRA software on clound)?
Can you give me an example, please.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just did this today, thank you. But a point of clarification: it only works if the property is added to the STATUSES, not the TRANSITIONS. Otherwise, it works great.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Accomplished by:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is a slightly difficult workaround possible. You can have a different workflow for Epics and remove the "Log Work" permission by restricting it on the different statuses in the workflow.
See http://www.j-tricks.com/1/post/2011/02/permissions-based-on-workflow-status.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What you can do is define a issue type screen scheme, and for the issue type Epic you remove the field - time tracking from its corresponding screens, so users will not find the field - Original estimate or Time spent field in the first place when they view the Epic.
However you include them for the other issue types.
Here's the link on how it is to be done
Hope this helps.
Rahul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Rahul, I have already done that so the Time Tracking fields do not appear on Epics. However, if a user navigates to the Epic in JIRA, they can use the 'More Actions' field and Log Work that way....is there any way to disable this option?
I guess the same question was asked here (https://answers.atlassian.com/questions/78960/time-tracking-disabling-ability-to-log-work-for-custom-issue-types) and the answer is no, has there been any change to this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.