Stiltsoft Table Filters, Charts referencing wrong Jira instance

[Trudy Claspill]

I am helping a client with the DC to Cloud migration.

In Confluence Cloud we have the Stiltsoft Table Filter, Charts & Spreadsheets for Confluence app installed. I am a novice with this app.

We migrated Confluence DC to Cloud initially to populate this product, creating a connection from it back to Jira DC.

We have just completed a migration of Jira DC to Jira Cloud on the same site.

Now Confluence Cloud shows two application links for Jira; the DC link and the Cloud link.

I have created a new blank page in Confluence Cloud. I added a Jira Issues macro to it and configured the macro to reference the Jira Cloud instance. That macro, by itself, returns data correctly from the Jira Cloud instance.

I then add the Table Toolbox macro to the page. I drag the Jira Issue macro into the Table Toolbox macro. Viewing the page in Edit mode the Jira macro still shows issues.

I then edit the Table Toolbox macro. It says "No issues found".

If I hover over the "No issues found" link I see that the Jira URL it shows is the Jira DC URL, not the Jira Cloud URL used by the Jira Issue macro.

Does anybody have any insights as to why this might be the case (before I take the next step of asking the vendor)?

When I look at the Application Links page for Confluence Cloud this is what I see.

The Jira DC link is shown first. I see no way to change which one is listed first.

We are not ready to delete the application link to Jira DC, though I assume if we did that then the problem might be resolved.

[Trudy Claspill · Accepted solution]

I think I found part of the problem.

In my testing I was using the newer Jira Issues macro.

If I instead used the older Jira Legacy macro, then within the Table Toolbox configuration highlighting the Jira element would show that same results as the Jira Legacy macro.

The next question to answer is if it is a known limitation of Table Toolbox that the newer Jira Issues macro is not supported, or is there also a problem related to having multiple Jira application links.

[Stiltsoft support]

Hi @Trudy Claspill ,

Yes, it's a known limitation due to the lack of support of the new Jira Issues macro regarding the 3rd party macros.

You may read the details here in our documentation: https://docs.stiltsoft.com/tfac/cloud/faq-using-the-app-188612625.html#FAQUsingtheApp-IstheappcompatiblewiththeJiraIssuesmacro?

Also if you have any other questions regarding the app, please contact our support directly (all the tickets there are registered and security maintained). Here we try to find related questions manually.

An update for other users who may come across this thread: please vote for the public ticket about new Jira Issues and 3rd party macros support 

https://jira.atlassian.com/browse/CONFCLOUD-77443

[Trudy Claspill]

@Stiltsoft support 

Thank you for your reply.

I did open a support ticket, after posting my question here in the community. There has not yet been any response on it.

https://stiltsoft.atlassian.net/servicedesk/customer/portal/14/TFCS-6316

[Stiltsoft support]

There are several people in the support team and sometimes there may be a delay regarding different timezones. The ticket isn't gone somewhere and will be processed in a proper way. 

[Trudy Claspill]

I understand that processing support tickets, especially when it is not a critical issue, takes time. 

Asking multiple sources the same question (community, work colleagues, support teams) simultaneously can get answers faster than relying on a single source.

Sometimes members of the community have answers to our questions and may respond faster than support teams that are handling high priority issues.

[Stiltsoft support]

Yes, you are correct regarding more general questions. But if you have smth specific (for example, SQL query for the Table Transformer macro), we prefer the support portal: it is confidential and you can freely share the screenshots and storage format (we can recreate exactly your page with the source tables and macros with all the current settings/queries). It simplifies the case and helps us to come up with a more precise solution.

Besides, different users from the same company may come with different questions regarding the same big task and it is much easier to follow their common history and look at the case at a global level.

But, nevertheless, here we also browse for related questions.)