Caterina Curti Atlassian Team

Hi @nimpla, Bitbucket Server provides a personal dashboard that contains your recent changes to the source code, the pull request created by you and that you are reviewing and a list of the most recently viewed repository as well as a search box to look for the other ones. This dashboard cannot be customized, but it would…

@muzematik, If I read correctly your edit, changing the config to the following resolved all issues: ProxyPass / http://my.business.com:7990/ ProxyPassReverse / http://my.business.com:7990/ Is this right? That would match our Securing your Atlassian applications with Apache using SSL documentation. Cheers, Caterina -…

Hi @David Rosenfeld, It looks like you may be running into this known issue: - FE-3912: Fisheye mail doesn't work with SMTPS The bug report above also contains a workaround that you could try. Cheers, Caterina - Atlassian

Hi @Mathew Benson, The "read" permissions on a repository allows the following: - Browse a repository - Clone, fork, pull a repository - Create, browse or comment on a pull request To answer your question, it is not possible to restrict this further and prevent the pull request creation. Cheers, Caterina - Atlassian

Hi @builder, I would highly recommend performing a full restore of Bitbucket Server (including the database and the filesystem) using a backup created before the git gc was performed. This is the most efficient and safe way to entirely recover the status of the repository. Is that an option for you? Cheers, Caterina -…

Hi @Adriana Berechet, The Permissions documentation page cover the details regarding the Fisheye permissions regarding repositories. To answer your question, users will not be able to see the repositories unless the permissions setup allows that. Permissions can be set on each individual repository or globally for all of…

Hi @Joyce, The visibility of the reviews is controlled by the permissions in the permission scheme. I would start the troubleshooting by making sure that all projects have the expected permission scheme assigned and by reviewing the "View" permission settings in all the used permission scheme. Maybe a default (e.g. "All…

Hi @David Dudenhefer, At this stage, I'm not aware of any options to exclude committers when using a CVS repository in Fisheye itself. More details on this scenario are available on the Restrictions on FishEye Starter Licenses page. In term of configuration options, it is true that the settings are limited to the ones…

Hi @Joshua Collins, Let me start by saying that this is an exception and we don't support database changes to the Bitbucket Server schema. However, I discussed this with the developers and under the current circumstances, to resolve the problem we will need to drop that column. For anyone else reading this, the following…

Hi @Cong Hieu, You can follow the instructions on the Import a repository page to import a Bitbucket Server repository to Bitbucket Cloud. The Bitbucket Server repository needs to be accessible by the Bitbucket Cloud site for the initial connection and the import to succeed. Alternatively you can push the cloned repository…

This is very interesting, the REPOSITORY_ID column should have been removed as part of the 5.4+ upgrade. Can you check if there are any values?

Glad to hear that Bitbucket Server is now up. I would like to know more details about the upgrade to better understand what may have gone wrong. Can you share the following? - previous running version (if relevant) - upgrade method (installer or archive) - the documentation that has been used and was not clear Cheers,…

Hi @Hovig Deveijan, Are there any errors in the atlassian-bitbucket.log (in the $BITBUCKET_HOME/log) folder? Can you share them here? Thanks, Caterina - Atlassian

You can find the Fisheye logs in the <FISHEYE_INST>/var/log folder. Look for the latest one (atlassian-fisheye-YYYY-MM-DD.log with today's date) and paste the error here for our review. We can also try running the Log Scanner to see if there is a match against one of our known issues.

Hi @Joshua Collins, I see. Since the upgrade to 5.11.1 did not help, can you please also share the following? The output of this query: SELECT * FROM plugin_setting WHERE key_name like '%AO_6978BB%' The table structure (in particular the available columns) of the following table: AO_6978BB_RESTRICTED_REF

Hi @Joshua Collins, From the log snippet, it looks like another Bitbucket Server environment (maybe a Dev one) may have been connected to the production database and upgraded the schema. To confirm that, we can run the following query and this will tell us which changes have been applied to the database and when: select *…

Hi @jpinczynski, Did you already check the permissions on the project and the repository for the affected user? This page provides an overview to the permissions documentation at the various levels: - 4 Levels of Bitbucket Server Permissions In this case, I would start by checking the project and the repository ones to…

Hi @Peter Dyballa, It seems like Fisheye is up and running but users cannot authenticate when using the Crowd/Jira user directory. Does this seem plausible? Is the user interface available at all for log in? Since the user directory is not functional, you can try to authenticate with the Fisheye password (note this is just…

Hi @Collin Plasse, Would it be possible to share the entire stack trace (from the logs) for the error as well as the lines right before and after this? In particular, we need to see the "Caused by" lines to understand the root cause of the issue. The java.lang.IllegalArgument message is a generic one that can be reported…

Hi @M Muir, Please have a look at the steps on the Recommended Action plan if a Repository Becomes Corrupted on a Bitbucket Server article and let us know if they help. They have been written with Bitbucket Server, the new name for Stash, in mind but they still apply also for older versions of Stash. Cheers, Caterina -…

Hi @Pankaj2204, In case you are using Bitbucket Server (hosted by your company), this is currently not possible. The rebase button is available to every user. It would be helpful if you could share more details on this request. This feature has been added to Bitbucket Server starting from version 5.5 and is part of the…

Hi, The information about the last login can be retrieved by following the steps / running the query on the following article: - How to query for inactive/idle users in FishEye/ Crucible This page covers both older and newer (4+) versions of Fisheye. Cheers, Caterina - Atlassian

Hi Anastasia, The information about the last login can be retrieved by following the steps / running the query on the following article: - How to query for inactive/idle users in FishEye/ Crucible Cheers, Caterina - Atlassian

Hi, The log confirms that the default branch does not exist. c.a.s.i.w.a.RepositoryAdminController Failed to resolve default branch. Cause: refs/heads/master is set as the default branch, but this branch does not exist In this example, the default branch has been set to be "master". Troubleshooting The following git…

Hi, It is likely that the issue is caused by an unsupported Java version as described in this reply. The Web interface does not load when running Fisheye 3.x article mentioned in the older replies has been updated to describe the possible root causes. Cheers, Caterina

Hi, If you are running an older version of Fisheye (e.g. 3.4.x), this is very likely to be caused by an unsupported version of Java. When checking the logs, you may find the following lines: WARN [main ] fisheye Run-sysinfo - Unsupported java version detected: 1.8.0_60 WARN [main ] fisheye Run-sysinfo - Currently supported…

Please refer to the article by the Atlassian Security team on this subject: - Atlassian Products & Services and CVE-2018-11235 & CVE-2018-11233 This covers Bitbucket Server as well as the other Atlassian Products & services. Thanks, Caterina - Atlassian

Hi @Andreas Scharf, I see that you were looking for a global option to configure that. Yes, that can be done as well by going to the admin area and click Defaults(under 'Repository Settings'). On the SCM Details tab, either select, or clear, the Show Checkout URL checkbox: More details on this page. Cheers, Caterina

Thanks @Ajay Madar for confirming this!

Hi @John Burrows, At this stage, the in-line file editing feature can only be enabled or disabled for the entire instance using the configuration option that you correctly pointed out from the bitbucket.properties file: feature.file.editor=false It would be helpful if you could share more details on the use case for this…