Use JIRA to create a status page in Confluence

Question

I think there's a way, but not sure how. Right now, I can create a filter in a onfluence page which lists all the open defects, and that's great, but not quite what I wanted.

Is it possible (and if so, how?) to create line items per defect (that update automatically) and that show the latest status updates from the comments? As in, filter for the defects, and then show just the most recent comment that has "status" or "update" (or some other codeword) in it.

For example, to look like this:

CASE-2384    The_Summary    Updated_Date    Status    Commentary_with_code

Clara Belin-Brosseau_Elements · Answer

Hi @Aidan Grey

In case you haven't found a solution yet, I can suggest trying our app Elements Publish which would definitely solve your use case.

Here’s how you can build a dynamic Confluence status page that automatically updates with the latest Jira issue data (like defect status or the most recent “update” comment):

1. Create a Jira filter that gathers all the defects or issues you want to display on your status page.

For example, all open defects from a specific project or component.

2. Set up a Confluence template in Elements Publish.In your template, you can include placeholders for Jira fields, such as: {{issue.key}} | {{issue.summary}} | {{issue.status}} | {{issue.updated}} | {{issue.comments.last.body}}

3. Configure the publication trigger.Choose when you want the Confluence page to be created or updated, for instance:

When an issue is transitioned to a new status, or

When a new comment is added that contains a keyword like “update.”

4. Publish automatically to Confluence.

Elements Publish will then create or update a Confluence page listing your defects as individual line items, each showing:

The Jira key and summary

The current status

The updated date

The latest status comment or update

This setup gives you a live, formatted status page that stays in sync with your Jira data,  much more powerful and flexible than a simple Jira filter macro.

I hope this helps :)

Aidan Grey · Answer

Thanks for this! I don't think it will work for our specific instance, but it DID inspire some different ways of thinking about it. Specifically, we are thinking about creating some new fields and bringing them in.

Brant Schroeder · Answer

@Aidan Grey Welcome to the Atlassian community

Not natively; the Jira Issue/Filter macro is showing fields which are available as column data - there isn't a comment field available.

We've gotten around this before using a custom field and automation - for example, we created a field called Last Comment:

* Create a custom paragraph field, called Last Comment - it doesn't need to be on a screen
* Create an Automation Rule to run whenever a comment is added, adding the last comment made into the custom field
* Visualize this in Confluence, as a field selected in the macro