search

microsoft / azure-pipelines-jira

Azure Pipelines for Jira
MIT License
15 stars 6 forks source link

Unable to connect Azure DevOps > Jira #26

Open brumargues opened 4 years ago

brumargues commented 4 years ago

Describe the bug We're unable to connect our Azure Devops to our Jira Cloud account.

To Reproduce Steps to reproduce the behavior:

  1. Install plugin on Jira Cloud
  2. Add organization
  3. Azure DevOps -- Select your Azure DevOps organization
  4. Azure DevOps -- Select a project
  5. Click continue
  6. Error Message: "The requested resource does not support http method 'GET'."
  7. Try again previous steps
  8. Error Message: "Service connection with name ** already exists. Only a user having Administrator/User role permissions on service connection ** can see it."
  9. The Azure account now shows up on the plugin in Jira, but we still can't get it on the DevOps

Expected behavior Able to select our Jira Cloud account on the Azure DevOps pipelines

Screenshots picturemessage_5z0fimot w2s

Desktop (please complete the following information):

JiriKovar commented 4 years ago

We're having the same issue.

kylebamfordpc commented 4 years ago

Us as well.

davidlundy commented 4 years ago

I've also experienced this issue on multiple projects and was able to find a workaround.

The Jira App needs to create a service connection in your DevOps organization and it appears to choose an id/name for that connection based on the organization name only.

If you already have a service connection with an identifier from your organization name you get this error message about a conflict because the service connection it is trying to create has the same identifier.

Renaming the service connection doesn't work. The display name gets changed but not the underlying identifier where the conflict is occurring.

The workaround is to replace that service connection with new one with a different name and delete the old one so the Jira App can have the identifier it wants.

Oddly enough I also had projects where the display name was the same but the identifier wasn't, and it was smart enough to put a (1) suffix on the end of the display name.

No code in this repo but I think this can be trivially fixed with a globally unique suffix on the end of the identifier.

dphildebrandt commented 4 years ago

Thanks @davidlundy this worked for us!

malandles commented 4 years ago

Worked for us too, thanks @davidlundy. A bit tired of doing workarounds with Azure but what can we do...

lsibilla commented 4 years ago

Hi.

I have found another way to workaround this:

Hope that helps.