Boris Berenberg - Atlas Authority Expert

You don't need to import anything. Just mention a JIRA ticket in a commit message and it will automatically link everything. https://confluence.atlassian.com/bitbucketserver/jira-integration-776639874.html

Trying following the exact format documented at https://confluence.atlassian.com/bitbucket/wiki-resources-296095206.html without piping the data in and see if the issue reproduces

Hmm, do you get any more info using --verbose 

Your proboem isn't your filter, it's your swimlane configuration. Go to Board Settings -> Swimlanes and set it to something other than Stories. 

Seems to work for me? Quick filter enabled, and assignee listed.

Do you mean Bitbucket wiki? Confluence wiki API would be a different URL.

I assume you are using jira-cli for this? https://marketplace.atlassian.com/plugins/org.swift.jira.cli/cloud/overview

Is this a server instance? It looks like Synchrony isn't working in your environment. https://confluence.atlassian.com/doc/troubleshooting-collaborative-editing-858772087.html

The assignee is supposed to be commicated based on the user icon. I think if you go to Board Settings -> Card Layout you should be able to add the actual name to the card as well.

Your assumption is correct. There isn't a great way to do what you're describing without setting up a new service desk for every single release. I would suggest you create pages which are sectioned by version and allow users to pick the version once they search drives them to it.

https://confluence.atlassian.com/adminjiraserver072/importing-data-from-pivotal-tracker-829827172.html

Can you elaborate? Do you not want a Kanplan view? https://www.atlassian.com/blog/jira-software/kanban-backlog-jira-software

I would start by just using a panel macro which says the max number. But off the top of my head, I don't know of any macro which does what you want. If you're on Server, then a user macro may be an easy solution? If cloud, then writing a connect add-on for this should also be fairly simple.

I believe that to do this you would need to manage checkouts on your own using script tasks. Bamboo doesn't natively support this functionality.

We just released Tableau for Confluence Cloud which alows for the same kind of functionality in Cloud.

Hmm weird, trying again https://confluence.atlassian.com/bitbucket/set-up-ssh-for-git-728138079.html If it doesn't work, try copy pasting it in

That is correct, if you want to stay with SVN you will need to buy Fisheye

Yes, I have dealth with the same thing. 9.5 and 9.6 are both unsupported https://confluence.atlassian.com/adminjiraserver072/supported-platforms-828787550.html

Go through the instructions at https://confluence.atlassian.com/bitbucket/set-up-ssh-for-git-728138079.html 

Take a look at these guys, I just saw a demo from them and it seems like it may do what you need: http://www.serviceclarity.com/

Eazy-Bi is the heavy hitter in the space, but it is also fairly complicated to use. I would search for reporting add-ons in the marketplace and pose your question to the vendors to see if they can tell you if their tool will do the job.

Are you on a supported MySQL version https://confluence.atlassian.com/crucible/supported-platforms-298977375.html

I don't know the answer off the top of my head, but I can empower you with how to figure it out for yourself. You can enable SQL logging: https://confluence.atlassian.com/jirakb/how-to-enable-detailed-sql-logging-in-jira-665224933.html Then put an issue into a sprint, then disable logging, and look in the logs to see what…

Are you on PostgreSQL 9.2,9.3, or 9.4? My guess is you are on 9.6, switch to 9.4 and it will likely work.

SLAs are based on events, not field values. I think the easiest thing would be to use a CSV import to update issues at the end of the…

I would try cleaning up the error and blank rows and see what happens. Also run your CSV file through some kind of validator to make sure you don't have an issue with quoting or seprators anywhere.

You don't. The team leaves you! Seriously though, take a look at https://bitbucket.org/site/master/issues/454/ability-to-remove-yourself-from and let me know if that helps

Deployment keys are to deploy. You need to install an ssh key, or push via HTTP.

https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.ext.subversion/server/overview

Do you mean between the node and the F5? Sure, you can either install the certs into Tomcat, or add a reverse proxy on each node to terminate SSL.