Mikael Sandberg Community Champion

Did you rename an existing status in your test case workflow, or did you create a completely new status called TC-Passed? From your description it sounds like you renamed an existing status, that would explain why all your other workflows are affected too, since statuses are shared across all workflows.

Contact Atlassian through their website or email them at support@atlassian.com and I bet they can help you with your account.

You may want to contact purchasing & licensing to see if it is still possible to buy JIRA Agile. Your other option would be to upgrade JIRA to 7.0 and upgrade to JIRA Software (JIRA + JIRA Agile)

You need to setup ssh, that way you do not have to provide a password. See Use the SSH protocol with Bitbucket Cloud

You could try InProduct translation for JIRA. If you do not want to use the plugin the other option would be to use a translation file, see Translating JIRA. The drawback of using a translation file would be that you have to redo the changes every time you upgrade.

Check to see that the group that your users belong to have Browse Users permission set under Global Permission. They made changes to the permission scheme in 7.0.x

Git does not allow you to select specific files that should be part of the merge, it is all or nothing. What you can do is create a new branch, check it out, and then use git checkout source_branch <file_path> ... The source branch is your staging and then specify the files that you want to merge into master. Once done,…

SourceTree is not the one tracking the file as binary, it is Git. When Git inspected the file it found characters that are not basic ascii characters so it thinks it is a binary file. You can use .gitattribute to change that, have a look at the documentation for Git Attributes

Do you have an account for it listed under Tools > Options > Authentication?

Okay, so you basically just want a report on how many hours your resources have worked? If you are using JIRA Server then have a look at Timesheet Reports and Gadgets for JIRA

Tempo Planner will do it.

Yes, it would be nice of you could do it using a global setting, but currently the option is to do it on each repo or use REST API to do it, and in your case I would probably go with the REST API option. There is an issue opened for it, BSERV-2792, so maybe in not to distant future we will see this option.

Yes, just change the permission to read-only on each project/repository. 

Are you trying to add the user to a group within Bitbucket? If you are using JIRA as your user directory you have to manage the group permissions from within JIRA, not Bitbucket.

If you give the group anyone permission to browse the project and set the share to everyone on the dashboard and any filters that is being used by the gadgets you will be able to share dashboards/wallboards without being logged in to JIRA.

If you are using SourceTree it will notify you when you need to pull (new commits on the remote). From the command line you can use git fetch.

Short answer is no. The issue key is not set until the issue is created.

There is no option in JIRA to do that, but there are plugins out there that can. User Deactivator for JIRA is one, or you could use the REST API and create your own plugin/script for it.

I did some research and it looks like 2.1 at least works with 10.9.5.

There is no download page for older SourceTree versions, but you could try and change the direct download path and see if it is still alive, http://downloads.atlassian.com/software/sourcetree/SourceTree_X.Y.Z.dmg. Just replace X.Y.Z with the version you want to download. 

ScriptRunner has a built in script that allows you to switch to a different user and you should be able use that to do the bulk edit and add that user to the watchers list.

It is possible if you use a plugin. JQL Tricks Plugin has a method to search by roles. 

What version of Git are you using on your client? I have seen the issue with the Clone URL string you get from Bitbucket have extra characters in SourceTree if you are using an old version of Git.

Git tracks file content, not files, so in your case Git detected that the new file was very much the same as the original file and recognized it as copied. This should not affect anything.

You need to use PUT instead of POST, and you also need to include id, version, title, description and reviewers in your payload, not just the new title. Here is an example using Ruby: def updatePullRequest(url, encode) put_request = { :id => 5, :version => 42, :title => "A change - updated via REST API", :description => "A…

Check out /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId}, the Put method allows you to modify the title, just send in the new title to replace the existing one.

JIRA itself does not have a clone functionality for projects, you can create a new project based on an existing one and that will share the schemes. If you are looking to clone the project with versions, components, project roles and issues then JIRA Command Line Interface has an option to do so.

Hopefully this should help you figure out where templates come into play https://confluence.atlassian.com/display/CAPTURE/Templates+and+Variables 

One option would be to make the repository public and share the link to it.

There are two ways of doing it, you could use the internal JIRA user directory and manually grant users access and that way control the user ID, but that would also mean a separate password. The other option would be to use Crowd, since Crowd allows you to setup user aliases in different applications connected to Crowd.