Jira Cloud OAuth migration orphaned all existing workitem/requirement links — need repoint or API-compatible auth path

[hanna_mueller]

Hi,

Thanks for reaching out!

The upgrade (so switching the API token integration to the OAuth integration) does not delete the integration, so the ID stays the same. Maybe you’ve accidentally deleted the integration and created a new one?

In any case, we can update all work items to use a new integration id via API
(And/or we can help you downgrade to an API token integration if needed).

I’ll send you a follow-up mail for the details!

Concerning point 2:

We’re looking into the issue - but it generally works also via OAuth, but there seems to be caching issue.
A quick workaround would be to first fetch the integration metadata in your script:

GET https://app.testiny.io/api/v1/workitem-integration/metadata?integration_id=77&all_projects=1

(and of course, replacing the integration_id with your id)

Alternatively, you can also create the workitem first and then map them to the test case or test case in a run. See more details in this post.

Best regards,
Hanna