-
Suggestion
-
Resolution: Unresolved
-
None
-
3
-
1
-
For Jira + Bitbucket integration, I would like the option to set branch permissions based on the person that an issue was assigned to. I can currently create a branch from an issue and assign that issue to a specific user, but I can't restrict changes on that branch to the assignee. Right now, I have to create the branch from an issue, and then go to the Bitbucket server to manually restrict that branch to a specific user.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BSERV-10985] Branch permissions based on Jira issue assignee
Maxwell Heeschen
added a comment - Sure John,
- It's important because if I have many branches with similar names and someone checks out the wrong branch, I don't want them committing to a branch tackling another issue. They should only be able to push to branches they were assigned along with an issue.
- When an issue assignee is removed/changed I would expect the permissions to change with that. I want to be able to associate a branch directly with an issue so that the permissions are related to the assignee.
- If a branch were deleted and recreated I would expect the permissions to not affect the new branch, unless you associate the recreated branch with an issue.
- If a branch were manually added through git then I would expect the branch to be locked to that specific user, but only if the defaults are set up that way. I could also see the branch being pushed and not having any restrictions applied to it.
I guess I'm basically looking for the ability to associate a branch with an issue more closely. In the last bullet I have, I would probably want the option to associate that pushed branch with an issue in Jira. In my specific use case, the users don't have a branch on the server unless it's an issue branch.
Thanks,
Maxwell
Maxwell Heeschen
added a comment - Sure John,
It's important because if I have many branches with similar names and someone checks out the wrong branch, I don't want them committing to a branch tackling another issue. They should only be able to push to branches they were assigned along with an issue.
When an issue assignee is removed/changed I would expect the permissions to change with that. I want to be able to associate a branch directly with an issue so that the permissions are related to the assignee.
If a branch were deleted and recreated I would expect the permissions to not affect the new branch, unless you associate the recreated branch with an issue.
If a branch were manually added through git then I would expect the branch to be locked to that specific user, but only if the defaults are set up that way. I could also see the branch being pushed and not having any restrictions applied to it.
I guess I'm basically looking for the ability to associate a branch with an issue more closely. In the last bullet I have, I would probably want the option to associate that pushed branch with an issue in Jira. In my specific use case, the users don't have a branch on the server unless it's an issue branch.
Thanks,
Maxwell Hi gorpmaster,
Could you expand a bit more on the use case for this? For example some things that might be interesting to add:
- Why is it important that a branch is locked down to an issue assignee?
- What would you expect to happen when the issue assignee is removed or changed?
- What would you expect to happen if the branch was deleted and recreated? (If branch deletion isn't locked down)
- What would you expect to happen is a branch was created manually and pushed via Git?
- Anything else you think is important? The more detailed your use case, the easier it is for us to envision how it would work holistically as a feature
Regards,
John van der Loo
Developer, Bitbucket Server
Thanks for elaborating Maxwell
With regards to users checking out the wrong branch, is that an actual issue that you see occurring, or is it a hypothetical issue? FWIW the Bitbucket Server team uses issue branches extensively and I don't recall us ever having run in to that issue. (I'm not trying to invalidate your assertion, merely attempting to gauge how much of a problem it really is.)
If a branch is manually added through git and then pushed, if there is a Jira integration present and there is an issue key in the branch it should pick it up and associate it already and make it visible in the dev panel in Jira.
e.g. here is the **development panel in Jira for the issue I'm currently working on.