Open ghost opened 2 years ago
We are experiencing the same issue in our organization.
Same with my organization, as well. Uninstalling the app (using Jira Cloud) as well as deleting the service connection within ADO, both had no effect on this issue.
Facing the same issue. Integration stopped working and getting "The signature is not valid" error as well
Exact same issue for us. Stopped working a while ago
Got this one as well, I opened up a ticket with Atlassian and got back that a specific endpoint is not working. URL is below https://x-pipes.vsassets.io/_apis/public/Pipelines/Events?provider=jiraconnectapp&api-version=5.0-preview.1
Hope this helps Microsoft resolve this as it would appear that an endpoint might not be working anymore
We've had a succesfully working Azure Pipelines <> Jira connection for a about a year. Recently it just stopped working, failing to provide any environmental release information towards Jira.
I have tried to remove our connection via the /plugins/servlet/ac/com.azure.devops.integration.jira/azure-pipelines-post-install-page page, but on removal, it shows this error message:
We're experiencing exactly the same two issues unfortunately... Very disappointing as we rely heavily on the integration and it was working quite well for us.
Are you able to provide any updates on this @shashban @nishubansal? A quick fix would be greatly appreciated.
It seems like the Azure Pipelines App is now even removed from Atlassian's Marketplace... https://marketplace.atlassian.com/apps/1220515/azure-pipelines-for-jira?hosting=cloud&tab=overview
This doesn't look any good for us...
I found it on atlassian marketplace but it is not working anymore. It does not appear on Azure Devops service connection page. When I try to install manually, I got "Only service principal identity is allowed to perform this operation."
+1 Same issue
We've had a succesfully working Azure Pipelines <> Jira connection for a about a year. Recently it just stopped working, failing to provide any environmental release information towards Jira.
I have tried to remove our connection via the /plugins/servlet/ac/com.azure.devops.integration.jira/azure-pipelines-post-install-page page, but on removal, it shows this error message:
Invalid request: The payload does not match the hash provided.
Also, when trying to add the same organization again, it throws an error as well. Sometimes this one:
The signature is not valid.
Or an error like this:
It seems our AZ Pipelines <> Jira connection is in some kind of a corrupted state and unable to mutate in any way.
Is there a fix/workaround to resolve this issue? Perform a magic reset somewhere? Any help would be appreciated :)