You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
There are too many users with incorrect access in our Jira project. The developers who are working in our environment should be assigned the developer role. That role should only have the following access;
1. add comments to story level
2. add subtasks to a story
3. manage status on subtasks
How can we update with Subtask create permission to the Project Developer in Jira?
Hi @bharathkumar , thanks for your question.
As @Marko Blagus writes, typically, you can only restrict who can create or not.
Atlassian has provided a workaround for this here - How to restrict the creation of an issue based on issuetype | Jira | Atlassian Documentation
However, if you are on a free plan, you will not be able to modify the permission scheme so this solution will not work for you either.
I agree automation is a good idea, but on a free plan, everyone has all of the permissions to your project, I think this is the issue. Is there any possibility to move to a paid plan? I think unfortunately that is the only way to get more control of the permissions.
There is no permission for creating sub-task, there is only "Create issues" permission and it's on project level, not on issue type level.
Possible solutions are to remove Create issues permission from them and than maybe for issues that need developers create sub-tasks with automation or scriptrunner.