Is it possible to restrict the Create Branch option to certain issue types in Jira Cloud?

[Dean Kinane]

Hi there

We made a recent change in our workflow where began using Sub Tasks but have encountered a few issue with the BitBucket integration. 

When a branch is created from a sub-task it isn't linked to the actual User Story. This means that, among other things, on the Releases page you can't see if there are any outstanding pull requests as branches/pull requests for sub-tasks don't display.

This means manually checking every sub-task of every story to confirm all pull-requests have been merged.

What we would like to do is only display the Development field (which has the Create Branch link) on Stories or Bugs thereby preventing our users from creating a branch from a sub-task.

I've explored the usual Jira config for this type of issue but everything appears to be locked for the Development field.

Is this possible in Jira cloud?

Any help is much appreciated.

[Andreas Link]

Yes, you can, I have solved this.

Solution is to have a dedicated workflow for subtasks (as usual) and on each state of the subtask workflow you set the property...

jira.permission.viewversioncontrol.denied

...and that's it. Then the development tools are not visible in any of the states anymore, but can still be seen/used on e.g. overlying issues with another workflow.

Source: https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/