nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Repeatedly editing the same key on reports – Any Better Way?

Davi Eler Magalhães

Hi everyone,

I have to create multiple report variants every week, such as the one shown below. For each report, I need to open the Edit menu on several blocks and manually update the same test execution key in each one (for example, LA-245).

Is there any existing way to define the key once and reuse it across all report blocks, similar to a variable or parameter, instead of editing every block individually?

If not, it would be a useful enhancement to support a shared variable/key reference to make report maintenance easier and reduce manual updates.

Thanks!

Accepted answers

All comments

Marc -Devoteam-

Hi @Davi Eler Magalhães

How are you creating your current report, as this does not look like a an ootb function from Jira or Confluence.

Is this report made in Confluence or Jira or a 3rd party app or an external tool based on exported data from Jira?

Davi Eler Magalhães

This is just a confluence page. The reports, documentation and other documents on our company are organized as confluence pages. I'm using the Jira Issue/Filter macro.

Marc -Devoteam-

Jira macro's in Confleunce you place hard coded information for each macro you use.

So you will need to update this each time.

If you have Rovo enable, you could ask Rovo to do this for you.

Another way is to view the advanced details of the page and use this, this should provide the page content showing all the macro's and their config, to make an API call using the Confluence api on updating page. You will need to provide the whole page content in the update call, replace the previous key with the new and execute the call.

Davi Eler Magalhães

How do I view the advanced details of the page?

Sergii Khomenko

Hey @Davi Eler Magalhães
As far as I know, there is no built-in way to do this. Confluence Cloud does not have variables, and each Jira macro stores the key internally. The only workaround is to use a script via the REST API: copy the page, replace the key within its content, and save the new version.

Davi Eler Magalhães

Ok I understand. Is there any possibility of features like this being added in the future? I've seen similar discussions that date since 2020.

CelesteCS

Hi, I'm Alexey 'Ce' from CelesteCS.

@Davi Eler Magalh ães, the native Jira macros keep the key inside each macro, as said above. If an app is an option, our CelesteCS Reporting for Confluence can take the key from the page itself, so you only change it in one place:

Instead of the Jira Issue/Filter macros, each block is a Reporting Table View with a Reporting Jira Data Provider. Its JQL can contain page variables that are replaced before the query runs: ${page.title}, ${page.id}, ${space.key} and ${today}.
Name the page after the test execution, e.g. LA-245, and write every block's JQL with the variable, for example issue in linkedIssues("${page.title}") or parent = "${page.title}", and any other filter you need around it.
Next week: copy the page (or create it from a page template) and rename it to LA-246. Every report on the page now shows LA-246, with no block to edit.
Each report is an ordinary Confluence table with the columns you choose, and can have totals, highlighted rows and filters for readers.

Documentation: Reporting Jira Data Provider (see Query – page variables).

The app is on the Atlassian Marketplace: CelesteCS Reporting for Confluence (free trial, Cloud and Data Center).

Ciro

Hi there,

There's no variable for this, but you can get close without any scripting by moving the key into a saved Jira filter and pointing every macro at it:

In Jira, save a filter with just the part that changes, for example key = LA-245, and note its ID from the URL (filter=12345).
In each Jira macro on the page, click the pencil icon and swap the key for the filter, keeping the rest of that block's JQL: filter = 12345 AND status = Done.
Each week, open the filter in Jira, change the key and save. Every block on the page follows it.

Use the filter ID rather than its name, since renaming the filter would break the reference. If several report variants need different keys at the same time, give each one its own filter.

If your blocks use Xray functions like testExecutionTests("LA-245"), Xray's docs say the first argument can be a saved filter too, but in Cloud those functions are still in a closed beta.

Davi Eler Magalhães

I would still have to paste the filter on all blocks of that week's test execution. Then create a new filter every week, since if i put the same filter everywhere it will also update the count of the blocks of the past weeks which is wrong because every week is a unique test execution.
creating a filter each week and pasting it on all blocks is more time consuming than pasting the key.

But thank you for the answer. I'll try to reframe the report so I can use this filter strategy!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira

jira-software