I want some of my users to have permision to create an issue but not want them to have allowance creating a sub-task or clone an issue which has been already created.
Does giving a permission to any user for creating an issue mean giving them allowance creating a sub-task and cloning?
This requirement can be achieved with workaround only. Add a Validator to the 'Create' transition to restrist the user/group to create sub-tasks.
Hope this helps you,
issue has already submitted for this feature, check this
same Q here
I can see that there are issues and questions about the same subject but there is no solution. Suggested solution's -adding validator- consequeances -allow users to fill whole screen and say them sorry at the end- are not desirable. There must be another user friendly solution.
you can hide the crea subtask option from issue operations menu, check the following Q
We have similar issues with cloning In a couple of projects. Users clone an issue, but then do not have edit permissions to modify key details. We have good reasons for not granting edit permissions in those projects and we expect our users to "remember" that they should not clone in those projects.
I understand that clone would not be permitted if we remove the "create issues" permission, but we do want our users to be able to create new issues in those projects.
Would it be possible to make the "clone" action depend on both "create issues" and "edit issues" permissions?
That would solve most of our problem with regards to cloning.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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