Excel add-in for JIRA OAuth

[Antony Kent]

I have installed the JIRA add in for Excel. This used to work OK but now keeps importing from the wrong JIRA source. I have unsinstalled/reinstalled the add in, disconnected the source, connected to another (the correct) source, but the add in keeps reverting to the default (incorrect) data source. Changing the source on the OAuth page is accepted and says its successful but when the JQL filter is input it reverts to the old data source.

[Levente Szabo _Midori_ · Accepted solution]

This is fairly typical for the add-in. If you search for it in the community, many people report problems with it. I collected errors with Jira Cloud for Excel and how to fix them.

One thing you can try is clearing the browser cache. It solved the problem once.

[Antony Kent]

Thx - for the link with the various suggestions. I have tried them all, including clearing the cache, uninstalling/reinstalling the add-in, disconnecting and reconnecting to a different JIRA space.  Each time the add-in appears to be successful i.e. the Oauth page says connection to the correct JIRA space is successful, but when the JQL filter is added into Excel it defaults back to the original JIRA space.  Using the export feature directly in JIRA works in that when (in the correct space) I use the filter to select the issues required, then click the small export to Excel - it exports correctly. I can then open new sheets in that specific XLS and the correct space is retained. However once I finish with that XLS file and open a new one the original problem returns - ie the add in is looking in the wrong JIRA space. Seems having exhausted the common causes the advice is to wait and it might go away on its own :-) ?

[Levente Szabo _Midori_]

Yes, pretty much sounds like it. In the article, I also suggest giving Better Excel Exporter a try if you can't afford to struggle with these inconsistencies. Have you done that?

[Antony Kent]

Thx for the link to Better Excel Exporter - looks like a much more functional solution. I'll forward as a suggestion to our Atlassian team - would require a company licence purchase