I'm not sure they answer my question because in the response,"In the post-function of the "create" transition of the issue workflow you can add validations to check if the user belongs to the group which can create the task issues or vice-versa" The way permissions are broken down is if a person can create an issue type, he can create ALL issue types including Epics. We want to limit a group to create all BUT Epics. If this can happen "out of the box" then fine but if programming or scripting is involved then it might not be a viable solution for us.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
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