Mikael Sandberg Community Champion

They replaced it with the release hub, and you can get some of the same information from it. I do not know the reason behind removing it, I believe it was around the time they were moving to three different Jira offerings. You could recreate most of the statistics using dashboards.

This message is expected, You get it if the project have more then one issue type and they do not share the same workflow. For example, I have projects that have three issue types and each have their own workflow, and you will see this message every time you edit an issue in the project.

Okay, so in the new Jira Cloud UI you have to go to the Issue detail view in order to manage watchers, it cannot be done from the pop-up when you click on it on a board.

Are you using Jira Cloud or Jira Server? I see the eye icon in Jira Cloud when looking at the detailed view via a Board, not on the Server.

Hi Katy, Welcome to the Atlassian Community. Nothing in 7.10.2 have changed that affects how you add watchers, you still just click the number next to Watchers and that will bring up the screen where you can add watchers.

I would contact support@bigbrassband.com since they are the vendor of the app.

Hi Anina, Welcome to the Atlassian Community. In order to create an issue you first have to enable the issue tracker feature for the repository. From the repository select settings, select issue tracker and then select if the issue tracker should be private or public. Take a look at Enable an issue tracker for more…

If the fields should always be required no matter what status the issue is in, you need to change the field configuration, have a look at Changing a field configuration. If the fields should only be required for a specific status transaction, you can use workflow validator to make a field required, see Advanced workflow…

Hi John, Welcome to the Atlassian Community. The limit is not in Bitbucket, it is within Git for Windows with the combination of LFS that has issues with files >4Gb, take a look at Git LFS issue #2434 for workaround.

According to the documentation you should see Create Branch under the development information, if not I would recommend contacting support@bigbrassband.com to get help.

Hi Liliana, Welcome to the Atlassian Community. The short answer is yes, you can change the workflow for one of your projects. If all three are sharing the same workflow you need to create a new workflow for the project that you want to change. Note that if you rename a status it will affect all workflows that is using…

It looks like Git Integration for Jira is able to allow you to create branches from the issue in the same way the Jira/Bitbucket integration allows you to.

What errors are you getting?

Hi Pawel, Welcome to the Atlassian Community. SourceTree stores user data under: ~/Library/Application Support/SourceTree ~/Library/Preferences/com.torusknot.SourceTree*

There is an issue logged for this, SRCTREEWIN-8743, and it looks like they are working on fixing it.

What do you get in return when running ssh git@server.company.com git-lfs-authenticate "repository" download Jenkins error code 128 indicate that it is using the wrong ssh key when trying to connect to Bitbucket.

You can also get to the workflows by clicking the Jira icon > Settings > Issues > Workflows From here you can see all the workflows that you have.

If you have Administer Jira global permission you should see the pen icon in the action column When you click on it will create a draft version of the workflow that you can edit and once you are done you can publish you changes. 

You can only add the statuses that are available in the workflow that your project is currently using. To add a new status you would first have to add it to the workflow before you can add it to the board.

Hi Daniel, Welcome to the Atlassian Community. To add a status to the column, just drag and drop the status you want in that column. You can either move one of the statuses that are under a different column, or one of your unmapped ones. In your included picture the only unmapped status that you have is the Resolved.

git lfs init has been replace by git lfs install. After you pushed the bare repository back to Bitbucket, did you make a new local clone or just continued using your old repository? It is recommended to delete the old clone and create a new one, since your old clone still thinks that your files that was just converted are…

I went back and checked my notes I created when doing this and after I ran the gc on the repository, I also did git lfs init on it: BFG rewrites history, extracting files to lfs/objects and adding .gitattributes for LFS tracking. Now we need to strip out the large files,run a garbage collection and enable Git LFS on the…

When I ran it I used these steps, comparing them to what is in the Bitbucket docs the thing missing is the garbage collection before the push, but normally Bitbucket does its own gc when you push anything to it.

If everything went as expected the files handled by LFS will show up as regular files in the repository. 

Hmm, sounds like something failed during the conversion, have a look at this troubleshooting guide. You should be able to see the file when you navigate to it in Bitbucket or locally in your repository.

The objects are created when you push the converted repository back, step 5 in the link above. Note that if you have already run the git lfs install, you can skip step 4.

No, it just tells Git that files with that extension will be handled by LFS, the actual conversion happens when you run BFG for existing files. If you do not run BFG, existing file would not be handled by LFS.

Hi Chris, Welcome to the Atlassian Community. The order of events should be: * Download Git LFS * Install Git LFS using git lfs install * Clone and cd into your repository * Set which files to track with git lfs track * Commit the changes made to .gitattribute * Run BFG to change the Git history

On Bitbucket Server it shows up on the right-hand side in the pull request, and the merge button is grayed out until all checks have been fulfilled. Based on what you see on Bitbucket Cloud, I suspect that you have not enabled Prevent a merge with unresolved merge checks.

Hi Andrew, Welcome to the Atlassian Community. The merge commit contains the source branch of your merge, so if the hotfix branch was deleted you can always recreate it using that commit. You can also use git reflog to restore deleted branches, have a look at How to restore a deleted branch. We are using both Bitbucket and…