Mikael Sandberg Community Champion

What version of SourceTree are you using? What does the error message say? If you are using 2.1.10.0 you may want to checkout this thread about authentication issues. Hopefully that will help.

All remote branches are listed under Remotes > origin. The branches you see under Branches are only local ones.

The change was implemented to make the install faster and so you do not need admin rights. Here is the blog post were they announced the change: https://blog.sourcetreeapp.com/2016/11/16/adding-staged-updates-to-sourcetree/

Yes, it will turn off the Git Credential Manager for Windows, but not the one that SourceTree is using.

Yeah, looks like that option was removed in the cloud version...

You need to reset the CAPTCHA in order to preceed. In Bitbucket, go to your profile and you should see a button to clear the captcha. Once that is done you should be able to fetch again.

You can try this, run this in Git Bash/command line git config --edit --systemand remove helper = manager and save the change.Also run git config --edit --global and under [core] set askpass toaskpass = That should hopefully take care of it.

Under space tools you have a configure sidebar where you can remove the Blog link. This will not prevent users from creating blogs. If you want to do that then you need to remove the permission to add/delete blog and disable the blueprint.

When you create the issue, is the due date set? If you leave it empty it will not be shown on the detailed screen.

The Git requirement is listed under Supported platforms and the main Install or upgrade Bitbucket Server, but I agree that it is a bit hidden and should be more visible.

You may want to look at JQL Tricks if you are using JIRA Server. We use it to find issues that are blocked by issues that are currently not in an active sprint. project = X AND issue in linkedIssuesInQuery("project = X AND issue in hasLinks(\"is blocked by\") AND sprint in openSprints() AND status not in (\"Awaiting…

Okay, so I played around a bit in my test environment and this query works there: issue in issuesWhereEpicIn("issue in linkedAllIssues(CH-58, \"contains the scope\")") OR issue in parent("issue in linkedAllIssues(CH-58,\"contains the scope\")") OR issue in linkedAllIssues(CH-58, "contains the scope") OR issuekey = CH-58

Here is a query we use to get all issues linked to a specific epic: project = X AND issue in issuesWhereEpicIn("project = X AND issuekey = X-XXX") In your case your query should look something like this (I have not tested it so you may have to tweak it a bit): issuesWhereEpicIn ("issue in parent("issue in…

Are you using .gitignore files? If .edmx are not in the repository .gitignore file, have you checked your global .gitignore? Does the commit contain the .edmx file? 

You need something like ScriptRunner or JQL Tricks to do nested JQL queries. I have not used ScriptRunner's JQL function for it (we have both plugins), but we are using JQL Tricks to search for all issues and sub tasks that are linked to specific epics.

Components can be used to group issues into smaller sub sections, like UI, API, Hardware etc. You could also use it to organize your issues based on customers, areas, functionality etc. I use it to organize tasks base on the tool, its a quick way of for example see all my tasks that I have related to Bitbucket or JIRA.

I agree it would be helpful if there were a way to organize your filters. I did a quick search and there is a request for it, https://jira.atlassian.com/browse/JRASERVER-25386, but it is pretty old.

You could use ScriptRunner to do this. I have used it to do calculations whenever a field is edited in the issue.

If you need different predefined texts based on the issue type you need a plugin. I am using ScriptRunner to do that for one of our projects. I also found Default Values for 'Create Issue' screen when searching Marketplace.

We are in sort of the same situation, we are migrating to a new LDAP server and changing user names at the same time. After discussing this with Atlassian support the only way of preserving the ownership is to either do the renaming of user names in the existing LDAP, or migrate the user names over to the new LDAP server…

You could change the Permission scheme and limit who can move an issue.

You just need to get the Confluence license.

I am using the Automation module (comes with JIRA) to do something similar. It uses a JQL query to notify users if an issue has not been updated in the past two weeks.

Short answer is no. There is no sync currently, but there is a feature request for it, https://jira.atlassian.com/browse/TEAMCAL-113

Issues in your back log should not have a value for the Sprint field, so just search for Sprint is EMPTY, and then export your list view to Excel.

Okay, found out the answer, in case someone else is looking for it. The way of doing it is to first do the renaming of user IDs in the existing domain, sync it to JIRA (or any other Atlassian tool), migrate over to the new domain, and add the new domain as a new user directory in JIRA.

Categories for Bitbucket allows you to add one or more categories to each project.

What version of SourceTree are you using? As of 1.8.x the license model changed and you now have to sign in using your my.atlassian.com account.

The project types are just pre-defined project templates to make it easy to get you up and running with JIRA, it does not mean that they are just Scrum or Kanban or Simple software projects. If you look at them you will see that the difference is the default issue types and workflows, but you can always modify that after…

Yes, if you limit the admin rights on the project to only system admin.