Mikael Sandberg Community Champion

Hi @Grant Robinson, Welcome to the Atlassian Community. If you by shared mean the share button that sends an issue link to the user, that action is not stored anywhere, so you cannot search on it.

So with the username you get authentication failed error? Are you using Windows? Make sure that Credential Manager does not have your password stored, it has caused issues for my Bitbucket users from time to time.

You can limit what spaces a user can access by modifying the space permission, see Space permissions overview. From here you can set how can view the space, add/delete pages etc.

Maybe try adding your username, based on this thread I found on Gitlab community Gitlab is using the username and email setup on the machine. So based on that, try this: git clone http://your_username@gitlab.tvstyres.in/C816/demo-project.git

Hi @Irving Buelto, Welcome to the Atlassian Community. What version of Bitbucket are you on? Rebase Merge was introduced as part of Bitbucket 5.5.

Based on the URL I am guessing that you are using a self-hosted Gitlab environment? Did you get the URL from the project page in Gitlab? From what I can see from the Gitlab doc, if you get it from the /username namespace the URL is not correct, since that namespace only shows which repositories you have access to even if…

To give ldap users access to Bitbucket after you added the user directory, all you have to do is go to global permission screen and add them to the group that have user permissions, by default that is normally bitbucket-users.

There is currently an active issue with Bitbucket. You can check out the current status via https://bitbucket.status.atlassian.com/ and you can also subscribe to updates so you get notified if there is an issue with the service.

Hi @kp hareesh, Welcome to the Atlassian Community. Did you the the clone URL from the project page in Gitlab? Did it look something like this: * HTTPS: <a href="https://gitlab.com/gitlab-org/gitlab.git" target="_blank" rel="nofollow noopener noreferrer">https://gitlab.com/gitlab-org/gitlab.git</a> *…

The migration is pretty straight forward for Jira, you create a xml backup, install and setup Jira/Confluence on your new server, import the xml backup and the attachments from the old server to the new and you should be all good to go. You can find the instructions for Jira here, Migrating Jira applications to another…

Hi @kehein, Welcome to the Atlassian Community. In order to be able to edit a workflow you need to be logged on as a Jira admin. You can then edit a workflow under Jira settings > Issues > Workflows. See Working with workflows for more information.

Hi @[deleted], Welcome to Atlassian Community. What the the behind/ahead column is telling you that you have made changes on your branch that has not yet made it to the default branch (the branch Bitbucket is comparing against), meaning your branch is ahead. If there are changes on the default branch that has not yet made…

Hi @Mohammad Imran, Welcome to the Atlassian Community. Not sure if this question is still valid, but the short answer is no, there is no limit to how many clients you can have. The only thing that limit it is the number of licenses you have for Bitbucket.

Hi @Cougar1907, Welcome to the Atlassian Community. So the CSV file should look something like this: Ignore the headline, the Issue key and Issue id columns, those are just from the export of my existing project. The first row should contain the field names that you are importing. Then each row after that is the issue you…

Hi @aeharrison1 Welcome to the Atlassian Community. To replace the code in your repository, just to do a delete of the existing code and replace it with our copy. Once you are done, just commit and push it back to your remote repository.

Hi @John Adams, Welcome to the Atlassian Community. You can find information here about Atlassian Support End of Life Policy, and it looks like 7.5.1 is already end of life. You can find all the documentation here, Atlassian Documentation and there is also a link there to the Developers doc. I can also recommend checking…

The only thing that may be a solution for this is to use the REST API to get the list, you would then query on the division first to get the project and then from there create the list. Or if each project correspond to just one division you could also use project category and then use that in your query to get the risks,…

Okay, and are multiple divisions using the same project? If that is the case then yes, I would agree with you that it is not possible to get that list unless there is a link between the projecthead and risks.

Okay, in that case I would say it would be hard to get that data out. Jira natively do not support nested queries, but I don't think even with an app that support it you could get it. Maybe take a look at scriptrunner since it has some powerful JQL functions, or maybe Power Scripts.

@Sven Erdtmann, if you use the project lead in your project settings to set it to your project head you could use project in projectsLeadByUser() in your query to get all the projects, like this: project in projectsLeadByUser() AND issuetype = risk AND division = abc

Correct, if you defined screens for all three issue operations you could remove the default screen.

7.12.2 was removed because of a bug and should not be used, see Issues resolved in 7.12.2 for more information.

Correct, the only two options for importing from another application is to use either CSV or JSON.

Atlassian removed the dedicated importers from other specific applications as of 8.4 an are now only providing importers for csv and json. See Importing data from Bugzilla

You're welcome, and the same to you!

Access keys are used to grant read-only access to repositories but you still want the user or service to authenticate against Bitbucket. You can find more information about it here, Access keys.

Hi Roddy, When you do the push to Bitbucket, do you get an error message? Also, go to settings for your repository to check that your key was not added as an access key to the repository instead of to your profile.

Okay, so this revealed that you have a pre-commit hook that is preventing you from checking in on master, see the second to last line. In Bitbucket, make sure you do not have a hook configured or branch permission set on master that prevents your push.

Have you added your ssh key to your SSH client? You can check by running this command: ssh-add -L If you do not see your key you can add it using this command: ssh-add <path_to_key> If you already added the key you can check that the key is associated with the right Bitbucket account by running: ssh -Tv git@bitbucket.org 

The default screen is used for unmapped issue operations, so if you have defined screens for create, edit and view then you do not need the default one. I usually only define screens for create and edit and leave the default one, and in some cases I only use the default one if the project do not require different screens…