Is there a Confluence Macro that can add a JQL statement to additional jira filters ?

asd asd October 5, 2020

Every time we set up a new page on confluence for a new release we copy the old one and change its Jira filters.

 

Is there a macro wich can add a simple jql statement,

for example "Release in (13.0, 13.1)" ,

to the filters of other Macros ?

 

So that we only have to change one filter each time.

2 answers

0 votes
Florian
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 5, 2020

Try PageTree Creator. It allows you to use variables that are being replaced like you may know it from templates. PTC brings a macro that can be wrapped around the original Jira macro. As the Jira macro needs valid JQL before it allows you to save it, you cannot work with placeholders directly. The wrapper takes everything without validation.

So it should look like this:

[PTC Jira macro with JQL "project=MyProject AND release IN (__releaselist__)" [Jira macro with some valid JQL]]

The inner JQL query will be replaced completely so it does not matter what you write here as long as it is valid. The outer macro will vaporize in the final page. 

0 votes
Christian Czaia _Decadis AG_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 5, 2020

I don't think that's possible (to have a filter which can be applied to all filter macros at the same time). 

Workaround could be to open up the copied page with the source editor: https://marketplace.atlassian.com/apps/1210722/confluence-source-editor?hosting=server&tab=overview

Search for all JQL queries and add / replace the desired releases

jql.png

Alternatively I would work with the versions in Jira, e.g. just filter for unreleased versions.

3rd option could be to just reference the filter in your JQL queries, e.g. filter = '10100' . That would at least save you a tiny bit of time.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events