Mikael Sandberg Community Champion

Yes, it is possible, the epic does not have to be in the same Jira project as the task/sub-task.

If you are listed as project admin you should see more options under the project settings, compare your screenshot to mine. When you created the project, was it created with a shared configuration? Or did you use one of the templates provided?

You would then have to have a pre-commit hook in Bitbucket for it. But if the user is not allowed to commit anything on his/her branch before a code review, the only way to access the code change would be in the user's local repository. The way we do it is that we allow users to commit code to their branches, but any code…

It looks like you have a hook on the repository that is verifying the committer. Bitbucket Server 5.0 added a new committer verification hook, see https://www.atlassian.com/blog/software-teams/enterprise-devops-bitbucket-server-5-bamboo-6.

Here is the link to the Cloud version of the documentation, https://confluence.atlassian.com/adminjiracloud/managing-your-workflows-776636587.html Based on the screenshots it looks like you do not have the right permissions for the project you are trying to change, you should see lot more options if you have project admin…

Okay, I would check that the application link is setup correctly by checking the troubleshooting guide above, and also Troubleshooting JIRA Integration Have you checked and see if you see anything in the logs?

What version of Jira and Bitbucket are you using? I found this KB related to the error you see, but it has been fixed in Jira 6.2.2 and higher. You should also take a look at the Application Link Troubleshooting guide to make sure your link is working.

In order for a commit to show up under the Development section in a Jira issue you need to mention the Jira key in your commit comment. The integration links Bitbucket with Jira in three different ways; via the branch name, you mention the Jira key in a pull request or when you mention the issue key in a commit comment. 

You can either create your own hooks for other processes like Memory Analysis, use Bamboo or Jenkins, or any of the many apps that integrate with Bitbucket. We are using Jenkins to do all of our builds and tests and is triggered once a user opens up a pull request. They are not able to complete the pr until all of our…

You can learn more about how to create project shortcuts here, https://confluence.atlassian.com/jiracoreserver/project-shortcuts-938846248.html. The only benefit I would see in connecting multiple Bitbucket servers to Jira would be if you are working with a customer/partner that have their own Bitbucket server, or if you…

Also take a look at this thread, https://community.atlassian.com/t5/Jira-questions/Link-a-bitbucket-repo-with-a-JIRA-project/qaq-p/789603#M254887, in there you will find a link to a request to be able to set a default Bitbucket repository for a Jira project.

@Derek SJust found this app, Linked Pull Requests, while looking at what was new on Marketplace.

The short answer is no, you cannot connect a specific Jira project to a specific Bitbucket repository. What you can do is create a project shortcut in Jira to the repository. The integration between Bitbucket and Jira is not per project, it is on the instance level using the Application links. And yes, you can link one…

Hi and welcome to the Atlassian Community. I removed your SEN number, this is a public forum so you do not want to make those available to the world. Since you have installed Jira Software already you also have Jira Core installed. Jira Software gives you agile functionality, including the ability plan agile work from…

Yes, Bitbucket Server also allows you to set conditions on your Pull Request (code review) like all reviewers have to approve, minimal successful builds etc. Take a look at Checks for merging pull requests. You could use Crucible in conjunction with Bitbucket Server, it all depends on how formal you want your code reviews…

Tasktop Integration Hub is another option.

You need an app to do it, I found IBM DOORS connector for Jira on the Marketplace, and I know OpsHub has a way of integrating DOORS with Jira, I looked at that option a couple of years ago.

Bitbucket Server does not allow you to commit/push via the API, instead you could to use regular git commit/git push to do it.

If you contact support at https://support.atlassian.com/contact/#/ they should be able to help you reactivate your account.

You may want to take a look at Scaling Bitbucket Server, it sounds like your server is running out of memory when you are cloning.

Have you tried to re-install it? Also check and see if you can see anything in the log.

Try and reset the password to admin, here is the hash for it {PKCS5S2}2ji+BcvOsgMOh5QGHHc+reOU2qvyHdf20E/0caC/Lf+u3+JvEst9prD15lLLpglJ

Follow these instructions on how to Restoring passwords to recover admin users

Right-click on it and select Checkout origin/..., that will bring up the checkout branch screen and from there you just select OK and it will create a local copy of the branch and setup the link to the remote branch.

Did you check under Remotes > Origin? You can also run git branch -r to list all the remote branches that your local repository knows about.

Hard will reset the index and working tree, meaning if you have made any local changes on master that has not been pushed to your remote, those will be deleted. 

You have to click on the commit you want to reset to, then you should see the option. You can also reset from the command line by using git reset --hard <commit to reset to>, or if you have not pushed your changes back to the remote master, you can use git reset --hard origin/master In order to see new branches created on…

This is a duplicate of https://community.atlassian.com/t5/Jira-questions/Restrict-Access/qaq-p/797854

Currently there is no integration between Bitbucket and Confluence, so you would have to write your own app/script to get the change log into Confluence. There is a feature request, CONFSERVER-30924, to get the integration and Atlassian is gathering interest for it, so vote for it and provide some feedback in the request…

Welcome to the Atlassian Community! It sounds like you never configured which screens the fields should be on, have a look at Choosing screens