No problem Erik, and thanks for the feedback. We do have plans to do this, however it isn't something we will have anyone working on in the next 6 months.

Thanks Megan, we will try that.

Based on the description of the plug-in it goes some way in fixing the problem. I would still welcome an official solution which could include more configurability and options for how the Create Branch dialog would select the most appropriate Repository.

Hi Erik, for Stash there's a 3rd party add-on you might be interested in on the marketplace. It will default the repository based on repo with the greatest number of commits associated with your JIRA project.

Cheers,

Megan Cook
Atlassian Product Manager

This seems to still be an issue – with Stash at least. We're hitting this pretty frequently since we have a lot of different repositories (for different customers) that our developers may be switching between multiple times a day. It would be beneficial if the Create Branch dialog at least knew which Stash repository/-ies have been connected to the JIRA project previously and default to that. If we, in addition, could configure a default repository (or list of selectable repos) for new projects, it would be even better.

Any update on the plans for such "smarter defaults"?

This is a problem for us too (with BitBucket) - it will result in branches being created in the wrong repositories.

Anyone know if this is something that could be easily implemented with a JIRA plugin? I've never created a plugin before so I am unsure if a plugin has the needed access to the internals to do this, or if this really is something that needs to be supported in the core product.

I would also like to see this fixed in stash. I've spent many times trying to figure out why my branch wasn't showing up in git to only realize it was made in the wrong project. I'm assuming it shouldn't be too hard to do.

I'd like to see this capability improved in Stash as well. We have a fork git workflow and we want the branch suggestion to be for the user's private fork of the master repo. This would have to a be a per-user customization of course since everyone will have their own fork.

When creating a branch from JIRA, Stash defaults to the most recently used repository for the user. We do have plans to provide smarter defaults in the future, but we can not provide a timeframe.

Could someone respond with a status or where it stands on your roadmap?