Hide "Create Sub-Task" button from Issue screen

Question

I've read quite a few posts on this, and none of them directly answer my question.  So I'm hoping someone has a good solution here...

I have a project where I'm using workflow and automation rules to create sub-tasks.  We're capturing approvals through these, and it is a highly regulated process.  The automation and workflow to create the sub-tasks and adhere to the process work beautifully!  The workflow transitions that set the fields used by automation rules to create the sub-tasks can be executed by users in the proper role.  And then we're using the automation account to create the sub-tasks with rules.

However, the option manually "Create Sub-Task" is still there, and that really messes things up.  I need to either block it entirely or figure out a way to fire a message to users to NOT manually create sub-tasks.

This looks like an option:  https://community.atlassian.com/t5/Jira-questions/How-to-hide-create-sub-task-button/qaq-p/2062716

But what I really want is a permission to 'create sub-tasks' that I can assign to roles.  Then users that aren't admins won't / shouldn't see the create sub-task button.  And the automation account still has permissions to create sub-tasks using workflow rules.

Is this possible?  Is there a way to create a permission tied to 'create sub-tasks' to prevent this?  Or is the only way to do this using scriptrunner per the post above?  Or is there another option I just haven't found yet?

Thanks!  Noah

Nic Brough -Adaptavist- · Accepted Answer

Welcome to the Atlassian Community!

No, it is not possible.

The doc you have found is for Server, and relies on Behaviours (which won't stop people from creating sub-tasks, it just makes it a little harder because the link won't be in the menu).

Behaviours for Cloud is not (yet) capable of doing that because of the limitations Cloud imposes on it.

There are no separate permissions for creating sub-tasks, it's a flat "can create issue (or not).

The best you could do is put in an impossible validator on the create issue transition, one that validates that the user is the Automation user and blocks the issue create.  But that is ugly for the users - they lose all the data they've entered.

Noah Miles · Accepted Answer

"The best you could do is put in an impossible validator on the create issue transition, one that validates that the user is the Automation user and blocks the issue create.  But that is ugly for the users - they lose all the data they've entered."

This might be a workable stop gap until the feature request above is released.