Jira Filter/Issue in Confluence for Jira Kanban Release

[Mike]

I was hoping to get the same functionality in my Confluence retrospective of a sprint task report for example in Confluence:

Insert More Content >> JIRA Issue/Filter
Insert: `sprint="sprint x"`

Which provides a great grid of all the tasks but with Kanban I can only release issues from the board. I want all those done issues to be in one location that I can report on in my retrospective so I would love to be able to insert the JIRA filter `release="Release X"` or something like that.

Is this possible?

[Ryan Kearney · Accepted solution]

Could you change the Jira filter to say something like 'sprint = "sprint x" and status = closed' or maybe resolution = done instead? 

[Mike]

Well, I am trying to get sprint reporting functionality out of a kanban project so I am not actually using a sprint which means I can't use the "sprint=..." query. I need to do something else to capture the done items in my kanban board.

Currently, I release from my kanban board to clear the done every other week. So I will give it a title "Release 2" but to my knowledge this is just releasing the issues from the kanban board not actually creating a grouping of those issues. I want to be creating a group of those issues so I can call them in the query, like in this case: Release="Release 2" to get the task raport table.

[Ryan Kearney]

I see. So I think that the field that contains the title of your release will be "version" rather than "release". 

[Mike]

That is what I was hoping but when I give the release a "Version name" of Release X

The query Version="Release X" 

I get the error message that JIRA did not understand the search query.

[Ryan Kearney]

Ah okay, try using the ~ instead of the = for the query. 

[Mike]

So the Query would look like this:

Version~"Release X"

Correct? That doesn't work either.

[Ryan Kearney]

Version ~ "5.1" with the space in between. I copied that JQL directly from my production instance where it returned results.

If that doesn't work, it may be due to the values in the Version field not matching the search parameters, or there may be multiple fields named Versions and you would need to query on the custom field ID which contains the values instead of the field name. 

[Mike]

I just tried to do this and it isn't working for me. Here is a screenshot of my JIRA releases with the test release today. Then the "Insert JIRA Issue/Filter" form where I am trying to insert the table from. But I get the warning shown.

Not sure how I would do this by a custom field ID, it would be easiest to do it on the field name.

[Ryan Kearney]

I wonder if there is an issue with the JQL through Confluence. Can you try and do the search inside of JIRA and save it as a filter to see if that works? Then you can pull in the filter through Confluence rather than using the JQL. 

[Mike]

Ahh! I figured it out. This is the query I am looking for:

fixVersion="Release 20180426"

Thanks Ryan, I appreciate your help!

[Ryan Kearney]

Ahh, I should have realized it was fixVersion sooner! Glad you figured it out. =)