Jira Cloud integration syncing wrong instance (QA instead of PRD)

Hi all, hope anyone may help me.

I’m trying to setup an integration between a Jira Portfolio Project and a common project in Asana, but when installing Jira Cloud app, even when I select my PRD Jira’s environment, it finishes the setup and syncs with my Jira’s QA environment.

I’ve already tried to remove and reinstall; started from scratch on a new asana project; and even re-installing and choosing the QA env instead of PRD, but it keeps syncing with QA env.

Another issue I also found was when removing the app and re-installing, all first setup screens were skipped and was not possible to choose the desired environment again. Since it’s not possible to change that after installing the app, the only turnaround I found was creating a new project.

Does anyone have an idea on what’s possible going on? I can share more information and screenshots if needed.

Thanks in advance!

Quick update here, Asana’s support replied saying this is a known issue and they are working to fix it but without an ETA.

Can we get an update on this issue since it’s been more than 3+ months since this issue has been reported?

Haven’t heard from Asana’s support since January. In my company (14K+ employees) we gave up on this since neither the support or their staff is worried about solving or at least communicating that this would be fixed. If they don’t care supporting a huge company like that, I don’t think they’ll care about anyone.

I have to say that I’m truly disappointed with Asana and in our company we decided to work mainly with other tools instead of Asana because of that.

I created a ticket on my end so I hope I can get more of an update.

Here is my response from Jira - I hope this provides some clarity:

I understand you are having some issues with Jira syncing to the wrong instance.

Asana’s Jira integration does not support authenticating to multiple Jira instances, and it is not possible to remove authentication from one Jira instance on the Asana side. Instead, please try to remove the app from the Jira instance directly (removing the app from the personal account is not sufficient). Here are the directions for how to remove the app from your Jira instance.

You should only need to remove the app from the Jira instance that you don’t wish to see data from anymore.

I hope this helps! If you continue to run into trouble, please don’t hesitate to let me know.

Best,

1 Like

Thanks for your support Kevin, I really appreciate it.

We already did it several times, we went on sessions with Atlassian Staff and Asana Staff (in different sessions) and did this and other actions with tem. With the Atlassian folks, we could identify that this is an Asana bug and they unfortunately couldn’t do anything about it.

What is happening in our case is really some unknown bug that only few users keep stuck within the wrong Jira instance (even we did select the right one) and the Atlassian support haven’t had an answer until now.

What we are doing now is creating our own integration between Jira + Asana with a dedicated development team because we also want to do more things than what the current integration does. If you have any other update, please send in this thread so more people can benefit from it.

Cheers!