Confluence Page Issues In Progress Macro Shows Issues from Another Project

[Daniel Burke]

I created a team-managed Jira project using the Kanban template and chose the option to have a related Confluence space built and linked/integrated. Within that new Confluence space, when I edit a page and try to add the 'Issues in progress' macro, it winds up showing issues/tickets from an entirely unrelated Jira project. None of the Jira issues from the related project show up; only the unrelated project's issues show. Many of the other issue-type widgets/macros have a field where I can specify the project to pull issues from, but not this one. I'm lost on how to use the 'Issues in progress' macro, getting it to show issues from the actual, related Jira project.

My Jira project and its related Confluence page share the same key of 'JST':

But when I add the 'Issues in progress' macro to a page in the JST Confluence space, it ONLY shows issues from an unrelated Jira project with key 'SMM'.

[Marc - Devoteam · Accepted solution]

HI @Daniel Burke 

Welcome to the community.

The issue is related to the search/filter/jql in the macro.

The macro doesn't know that the space and pages in it are linked to a specific Jira project.

The macro you are using is able to display Jira issue information in Confluence, based on the criteria set in the macro.

See the macro documentation, here.

SO if you simply add the macro and the search criteria, says status = "in progress".

The macro will show all issues from all Jira  projects where you have access to that are in progress

This marco search works the same as searching in Jira

[Daniel Burke]

Thanks for the welcome and the reply. Unfortunately, I think you're talking about the 'jira issues macro' and not the 'issues in progress macro.' This specific macro doesn't seem to provide any wat to supply a filter/jql string/etc.

It seems like there's no config available at all to define which Jira project to pull issues from or to supply a filter/jql.

[Marc - Devoteam]

Hi @Daniel Burke 

Issues in progress, this just look at all your issues in progress. This is not a default macro from the Confluence product

It seams all your issues, so not related to a project, but in the Jira instance based on status or status category are being fetched by this macro

I suggest to use the ootb Confluence Jira Issue macro as this is configurable and default in the system.

Which marketplace app is providing this macro?

[Daniel Burke]

I have not installed any marketplace apps nor done any custom configuration. I created a Jira project and checked the box to have it create a linked/related Confluence space. So Confluence is providing this macro out of the box.

Also, it only shows the 4 'SMM' keyed issues when I create the 'issues in progress' macro. The actual linked Jira project is key 'JST', which certainly has issues in the in progress status. But the 'issues in progress' macro does NOT show those issues. It ONLY shows issues from project 'SMM'.

[Marc - Devoteam]

Hi @Daniel Burke 

I found the relation to this, see this Atlassian Support page

Most important on this page is:

For displaying basic Jira information, such as issues and charts, we recommend using the Jira Issues Macro and Jira Chart Macro as these macros have better performance and are easier to configure than gadgets. 

If the Jira information you want to display isn't available from either of these macros, a gadget will likely do the trick.

As of September 26, 2022, Confluence will no longer support Jira gadgets in Confluence.

Any existing instances of these gadgets will continue to work and be available to add to a Confluence page from the insert menu and using the slash command.

So these gadget could have wrong info and you should now use them anymore.

If I try in om my instance, I don't even get any information.

[Daniel Burke]

So strange. Yeah I'm able to display the tabular info I wanted using the standard Jira macro and a proper filter/JQL, so my "problem" is solved. I'm just confused how this other macro is so backwards and why we're seeing this strange behavior. I guess it just comes down to deprecation, huh?

Well, thank you for all the replies here. I really appreciate it! Guess it's time to retire those old macros.