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; } } }

Table Transformer - Only display "Duplicates" Issue Link not other types of Issue Link

Katie L

Hi all,

I would like to create a table with the epic keys and their Issue Links.

The tricky part is I don't want to display all the Issue Links, only the "duplicates" Issue Links.

My gut is telling me there's a way where I use SQL in Table Transformer to do this.

This is the JQL I used: project = "ProjectName" and issueLinkType = duplicates

The column Links is displaying all the Issue Links regardless of whether they're "duplicates", "relates to" or "mention in".

In my case the "duplicates" Link Issues have certain project codes (e.g. P1-, P2-, P3-). And the other types of Link Issues do not have these project codes

I'm thinking Table Transformer will be the way to do as my problem have some similarity to this question, where I think I need to write a query that splits up the Issue Link items within the one cell: https://community.atlassian.com/t5/Confluence-questions/Table-Transformer-Select-Through-Multiple-Items-Within-Key-Cell/qaq-p/1653652

Thank you so much, any help is appreciated.

Accepted answers

Katerina Kovriga {Stiltsoft}

Hi @Katie L ,

Please attach a screenshot of your Jura Issues table with the marked duplicate issues - maybe the Table Filter macro will do the trick? It is better for us to see the table before suggesting some tips.

All comments

Katerina Kovriga {Stiltsoft}

Hi @Katie L ,

Katie L

Thanks Katerina for your quick response.

I can provide an example of the Jira Issues Table with dummy data.

Key	Linked Issues
MOCK-123	MOCK-124, P1-100, P2-110, P3-111

MOCK-123 is the Issue key

The Link Issues’ relationships to MOCK-123 are as follows:

MOCK-124: relates to

P1-100: duplicates

P2-110: duplicates

P3-111: dependent

In this case, it'd be great if only P1-100, P2-110 are displayed in the cell. Thank you so much!

Katerina Kovriga {Stiltsoft}

As the case seems to be a tricky one, I've returned with a workaround that uses two Jira Issues tables instead of the one original table - please, take a look at the screenshot below:

Thu 4-1.png

The first tables remains the same: your Epics and their linked issues.

The second table should contain only all of your issues with the duplicate status - we'll need only the "Key" column, other fields are optional.

The two tables should be wrapped into the Table Toolbox macro.

Thu 4-2.png

Inside the Table Toolbox macro your tables should be wrapped into the Table Transformer and Pivot Table macro.

Here is the custom SQL Query for the Table Transformer macro:

SELECT T1.'Key' as 'Epic keys', T2.'Key' FROM T1
LEFT JOIN T2 ON T1.'Linked Issues'->indexOf(T2.'Key') > -1

Thu 4-3.png

The last step is to create a beautiful pivot table:

Thu 4-4.png

The result table looks neat and easy-to read.

Hope this will help your case.

Katerina Kovriga {Stiltsoft}

And you may also use an additional Table Transformer macro to rename the second column.

Here I've chosen a line break as a literal value delimiter inside the Pivot Table macro settings and used the following SQL query for the second Table Transformer:

SELECT T1.'Epic keys', T1.'Literal of Key' as 'Duplicates' FROM T*

Thu 4-5.png

Thu 4-6.png

Welcome!

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

Quick Links

Find more posts tagged with

confluence

sql

jira

cloud

confluence-cloud

jql