-
Suggestion
-
Resolution: Unresolved
-
None
-
11
-
28
-
Problem Definition
Currently, all users who has the View development tools permission will be able to see the Create Branch option. It would be beneficial if the Create Branch option could be disabled or customised as not all users should be able to create a branch.
Suggested Solution
Add another permission for Create Branch specifically or provide an option to disable it.
Workaround
None
- is related to
-
- Closed
-
- Gathering Interest
- relates to
-
- Gathering Interest
- links to
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-14931] Disable or limit the "Create Branch" option
we want to limit branch creation according to issue type. For example allow branch creation from Epic and Story, but not from Subtask.
I guess this issue can be solved by using the properties on the workflows, they work in the cloud, but should also work on the server, I guess.
Please find them here: https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/
An example could be to add the property jira.permission.viewversioncontrol.denied on any state of a specific workflow, which is assigned to an issuetype, where branching shall not be possible aka visible.
For our purposes, it would be good enough just to have a "disable" option for branch creation for subtasks. I have searched for a way to modify a screen to do this without any luck.
This is very much needed. Especially when you have Jira server integrated with Bitbucket cloud, using DVCS link (OAuth). Such integration is at instance level, and all projects and its users might see the btbucket repo which is linked (although a set of projects, users actually are code committers for that repo). There should be a way to restrict or map the Bitbucket repositories with specific projects in jira, or restrict the create branch option to only a set of users / projects which have the DVCS sync enabled.
We need an option where users should be able to only view the branches but should not be able to create the branches, which will be an useful feature. Also user/group level restriction will be very useful
We have defined the use of certain Jira item types to require or not allow code changes. having the ability to not show the create branch button on the issue page would be a great help in enforcing the policy.
Bump. Still an important feature to limit issues where Create Branch is not needed for a specific project or subset of users.
+1
Our company uses JIRA across all departments, but we encounter issues when branch names include non-ASCII characters due to the use of our local language. This often leads to compatibility problems with several dev tools. Therefore, it would be beneficial for us if there were an option to disable branch creation through JIRA when these characters are included to ensure better integration with our tools.