From your description, it has to be realized within the same project.
Not a beautiful solution, but it could work. You have to take the Field Security Plugin. Then you have to declare two groups of fields/custom fields. The one are only readable (Epic) for a specific role(epic writer, defect writer), the others read and writable (Defects). If only one of the readable is mandatory and the user is in the role "defect writer only", then the user cannot create an Epic.
Yes for a project
i initially thought what you suggested but was hoping there was something else that I was overlooking. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can try to use workflow properties. You can read more about workflow properties here:
http://www.j-tricks.com/tutorials/permissions-based-on-workflow-status
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join us June 26, 11am PT for a webinar with Atlassian Champion Robert Hean & Loom’s Brittany Soinski. Hear tips, stories, and get your burning questions answered. Learn how Loom makes training and enablement easier. Don’t miss it!
Register todayOnline 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.