Thanks for the reply back, Ignat. I saw on answers.atlassian.com where a few people were talking about using the method you describe to attack the problem. They were talking about turning the panel off entirely for certain projects (rather than just hiding the "create branch" link) and seemed to be having mixed success at best. In general, I try to avoid using putting a lot of javascript in the announcement banner just to overcome UI issues in the product anyway.

For now, I'm trying to get people to just live with it. On the old source tab, we could configure the number of files shown for each commit before it tosses you over to fisheye to see more. I don't see a way to do that here either, which is not helping me make the case that this is an improvement. :-/

Hi Dave, 

Unfortunately we are not planning to update the current development panel in the foreseeable future. I've read your comment before where you explain that it's not easy to remove the panel as some developers in your organisation do use the feature.

The idea is to add a custom field that would execute a javascript and customise the panel for you, i.e. which would allow to hide the panel for some developers.

 This is not officially supported - but can solve the problem for you until you migrate to git.

Some related links:

• https://confluence.atlassian.com/jira062/fields-allowing-custom-html-or-javascript-588581450.html
• https://answers.atlassian.com/questions/45825/how-to-remove-options-from-a-multi-version-picker-field

Cheers,
Ignat
JIRA Bugmaster.

Not that anyone will see this, but after two years we finally caved in and enabled the developer panel. We have more teams on git/BitBucket now, so we really wanted the extra functionality provided.

On the negative side, this issue still hasn't been fixed, so we have to explain to developers who are on projects that are using subversion/fisheye/crucible that they should not click on the "create branch" link. And we also have to explain to all developers in general that we can't suppress the "create branch" link when it shouldn't be shown (i.e. project isn't using BitBucket, or isn't applicable to a certain issue type or status).

To make matters worse, all the email I'm sending to our developers from Jira on this topic get delivered with messed up sender name thanks to JRA-30224. So half our team thinks Jira's email is some kind of spam or phishing attempt. Really crappy user experience all around, Atlassian.

@Oswaldo - You're missing the point. These ARE projects that are meant to track development. In our case, they use subversion together with fisheye/crucible. They are linked with project level links to the relevant fisheye repositories and crucible projects. And yet... the developer panel contains a link that says "create branch..." that takes the user to stash.

Apparently, Atlassian has migrated 100% of their repositories to stash, but for those of us who haven't (and are only at the beginning stages of migrating several hundred), this is a highly disruptive bug. Most of our developers don't even have an account on stash at the moment, so they can't login there. And the ones who CAN login are confused about why they should be creating a branch in stash – they keep looking for their (subversion) repository to be there....

Hi swisscom.scm / circusdog,

This might be solved by customizing the permission schemes for projects that are not meant to be used to track development.

Consequently, could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances

The credentials should be the same as for this site (https://jira.atlassian.com).

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

In our environment, we have 300+ projects in jira that are mostly using subversion together with fisheye/crucible. Only a handful of projects are using stash because we're still on the early side of figuring out how we're going to use this and roll it out. When we integrate the stash server with Jira, however, all 300+ projects suddenly get a "create branch" link that takes them to stash. This looks really amateurish and created all kinds of support questions and complaints for us. As a result, we have disabled the developer panel, which really hurts the projects using stash because we'd really like for them to be able to create branches from the link on the jira issue.