Mikael Sandberg Community Champion

Okay, so the first error message indicate that your username or password is incorrect, so you should make sure that the password stored in Sourcetree and Windows Credential manager is correct. 

Okay, so in this case your repository is empty, so the only way to create a branch in it is to first clone it and then do a commit in the repository. The initial commit will create the master branch. Once that is done you need to push your commit back to Bitbucket and then you will be able to create branches from within…

Hi @Vito Kurnik, Welcome to the Atlassian Community. Do you get an error message when you try and push? And if so, what is that error message? 

Hi @Plotva, Welcome to the Atlassian Community. To create a new branch in Bitbucket Cloud just click on Branches and you will see a Create branch button. In Bitbucket Server, click Create branch on the left side menu bar.

No, you can configure the branch permissions anytime on the project level. It is only if you set the branch permissions on the repository level and want to use a specific branch name that you first have to create the branch.

I think adding a comment on BSERV-10114 is the way to go.

Check your atlassian-jira.log under atlassian/application-data/jira/logs

Hi @Allan Ford Welcome to the Atlassian Community. It is possible, but your browser has to support it, only IE/Edge support it natively, and for Chrome and Firefox you need an add on. Your link in Confluence has to look like this, file://///unc/path/file.name

The command git diff master...branch will show all changes made in branch that have not yet been merged into master, same as compare against current in Sourcetree assuming branch is your current branch.

Hi @devops2019, Welcome to the Atlassian Community. Bitbucket allows you to set project defaults that will apply to all repositories within that project. But when you create a new repository, nothing is created in it until you make your first commit. That is when Git will create the master branch. So part of what you are…

Currently it is not possible to hide those pull requests. A pull request has three major statuses; open, merged and declined. I checked Atlassian's feature requests and this one, BSERV-10114, is about being able to filter on the ones that needs work.

Yes, once you created the new workflow, you cannot delete a status from an active workflow, when you replace the old workflow with the new one you will be asked to which status existing issues should be moved to when you publish the changes to your workflow scheme.

I agree with you that when you change the role to trusted it should also add the user to the individual groups. I see the use for the roles, it is a fast way of adding an admin without having to go into each group to do it. In regards to when you want to add someone as an admin for a specific application, then use the…

Hi @Chinedu Ezeonyim, Welcome to the Atlassian Community. By Active Directory integration I assume you want to have your users authenticate against your AD correct? If that is the case then have a look at Connecting to an LDAP Directory, that will guide you on how to setup a user directory against your AD.

When you make a user trusted, you basically give them admin rights to all your products, meaning they will also count towards your license automatically.

If you go to Administration > Groups you will see product access groups, they have a lozenge, or label, next to them saying Default Access Group. This is what controls the access to the application. You can find more information about product access here, Update product access settings. Please note that these groups are…

It is the group membership that controls who have access to Jira Service Desk. Besides going to the group and add/remove users, you can also turn the access on and off by going to each user and click the slider for each app. But if you look further down you will see that all it does it adding/removing your from the…

Correct.

From the Jira side there are no limitations either. When you click on create branch in Jira it will just bring you to Bitbucket and the create branch screen, and from here you can select any repository to create the branch in.

No, there is no way of reverting the move. Your only option would be to user a query to show recently modified and then move them back to the right issue type.

Hi @Brian, Welcome to the Atlassian Community. Yes, one Jira issue can be associated with multiple repositories. The way the integration works is that you can associate an issue by either adding the Jira key to your branch name, in a commit comment or mention it on a Pull Request. 

Check and see that nocount has been turned off, see Cannot insert the value NULL into column 'ID', table 'xxxxx'; column does not allow nulls. INSERT fails. 

Correct, the story point field is locked. Your only option would be to create your own custom field, just note that Estimations on a board can only be based on a number field, not a select field.

Hi @Susan Anglin, You should be able to get going with Jira fairly quickly, you can get a lot of information from this Community, and the documentation has really good tutorials. You also have Training for Jira which gives you access to short tutorials from within Jira.

The ssh-keygen generates two files, id_rsa and id_rsa.pub. You want to copy the content in id_rsa.pub into your profile in Bitbucket. So in step 2 your command should look like this instead: notepad ~/.ssh/id_rsa.pub

Make sure Windows Credential Manager has the correct password, it does not automatically update your password when you change it. I have a handful of developers that have this issue every time they change their domain password.

Make sure you copy all the characters in the .pub file, normally on Windows it adds a label at the end, that also needs to be included.

Hi @Paddy Byrne, I moved your post out of the spam quarantine. I guess is that it ended up in there because of the code block.

Have you logged on to your Bitbucket Server before? Usually your Bitbucket Admin sets up an account for you, either using LDAP as authentication or an internal user directory, so you should contact your admin to get your username and password. 

@Adam Wainberg A label can be removed, as I mentioned above you have to remove it from all issues that have the label in question.