Hello, I deleted some of the Jira issues from my project. These issues were reported on Confluence page using Jira Issue macro. I deleted these issues in Jira however the Confluence page with Jira Issue macro still show them in the report. Its not removing them from the report.
We are using Premium Jira version on Free Trial.
I use the Jira macro in Confluence with no problems. However we're on paid versions. I suggest opening an issue with Atlassian about the Confluence problem, providing you are paying for Confluence.
Then what is the purpose of Free Trial? If it doesn't work in Free Trial it won't work in paid version either.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sanjay Khanna,
That very much looks like an issue with refreshing the result set. Try refreshing the macro or - in edit mode - refresh the filter and save your page again. It's not what you would expect, but it may act as a workaround to - probably - fix your view of the correct issues in Confluence.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried refreshing the macro in edit mode and it didn't work. I have 10 tables using this macro in Confluence and this doesn't seem to be the solution for managing 20 epics in the project as PM will be editing, deleting and updating issues in Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I deleted and recreated the table in Confluence and it still doesn't work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have seen results in a Jira macro not correctly refresh in the past, @Sanjay Khanna. If that is so, that may qualify as a bug or at least an opportunity for improvement. I can't fix that for you.
What I can try to help you with is to work around the issue so the deleted issues no longer appear.
You've got me confused about the tables you mention. And they should not have any relevance to the problem here. Just for the sake of making sure we are solving the right problem and solving it in the right way, take these steps:
I would expect that you get the exact same results in step 2 (Jira) and step 4 (Confluence). If that's the case, replace your outdated Jira macro with the new one where needed. If not, you might want report this to Atlassian support directly.
On a side note: it's quite logical that you edit and create issues in Jira. As a best practice, I would recommend not to delete issues in Jira, but instead move them into a closed status (use the resolution field to indicate you've decided not to complete the work). Not because of this issue, but because deleting issues is literally destructive and leaves no trace of whatever was there. And Jira can perfectly handle hundreds of thousands of issues, so there's really no reason to physically delete them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What I meant by table is the essentially the table Jira Issue marcro creates when it runs the JQL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.