Jira Forge add-on "Link to Testiny" produces https://undefined/jira-forge-link#linkId=undefined

Support
1

Our Testiny org connection was removed earlier. Now the Jira add-on (v2.7.0) cannot re-link. “Link to Testiny” always redirects to https://undefined/jira-forge-link#linkId=undefined — both host and linkId are undefined.

Already verified/tried on our side:

  • Service URL correctly set to https://app.testiny.io (Connected apps → Data management)

  • External data-sharing with app.testiny.io approved

  • “Configure Testiny Connection” set to Testiny Cloud

  • Full uninstall + reinstall of the app

  • Created a new installation token in Testiny

  • API-token direction works (“Successful read from Jira”)

In DevTools → Network, the config requests (index.ts:362, sendEvents.ts:17) return HTTP 200, but the resulting host + linkId are still undefined. So connectivity is fine; the backend is not returning a valid link. How do we re-establish the Forge link / regenerate the linkId for this Jira site?

Testiny v1.38
4

Thanks for your post!

Jira shipped an update to the Add-on infrastructure (Forge) that is currently blocking new connections of the Testiny Jira Marketplace app to a Testiny organization.

We are working on a fix and should soon be able to release it.

Note that existing connections should not be impacted.

Thanks for your patience!

Best regards,
Alex

2

The Testiny Jira add-on is currently not working — we’re unable to see Testiny items within Jira. Is there a known/general issue on your end?

3

Jira add-on ‘Link to Testiny’ redirects to https://undefined/jira-forge-link#linkId=undefined (host + linkId both undefined). Already tried: full uninstall+reinstall (v2.7.0), creating a new installation token. API token direction works fine. Our Testiny org connection was previously removed. How do we re-establish the Forge link?

5

Hi Alex,

Thanks for the explanation.

I have to be honest, though: this should have been communicated proactively. We received no notification or status announcement about this issue on our end. Because of that, we assumed the problem was on our side and spent the entire day yesterday troubleshooting it — reinstalling the app, regenerating tokens, checking our configuration, etc. It disrupted our work and cost us a full day of effort that could have been avoided with a simple heads-up.

When a platform-level issue like this is known on your side, we’d really expect a status page update or an announcement so customers don’t waste time chasing a problem that isn’t theirs to fix.

We’d appreciate it if incidents like this could be communicated more transparently going forward. Please also keep us posted once the fix is released.

Best regards,
Selim

6

Hi Selim,

Thanks for the feedback! I completely understand your frustration about this issue and not knowing about it beforehand.

Frankly, we did not know either. We do have automated tests in place for existing integrations to Jira, but not for installing the Testiny Jira Marketplace app from scratch (we might try to add that, it is a bit tricky, though :grimacing: ). So that caught us off-guard and you were the first user to shoot us a note.

But you’re certainly right, we should communicate such issues either here in the forum (for more detailed issues) or on our status page status.testiny.io (for general issues) - and we will do whenever we can.
If you have problems with Testiny that seem to be out your reach, please don’t hesitate to post in the forums.

Just so know, we are actively working on a fix and the fix should be released to.

Sorry again for the trouble!

Best regards,
Alex

7

We have just released a fix for this issue with Testiny v1.38.0.
Again, we are sorry for the inconvenience!

Best regards,
Alex