Jira automation craate table of linked issues

[Alan Alder]

I'm trying to create a table within another field (acceptance criteria) using jira automation to display my linked issues however I can't get each issue to show on a new row.

[Bill Sheboy · Accepted solution]

Hi @Alan Alder -- Welcome to the Atlassian Community!

You are iterating over the issuelinks inside of the table row formatting.  Try moving the iterator outside of the row's conditional check.

For example:

*Delivers Tickets*
||*Ticket*||*Status*||
{{#issue.issuelinks}}{{#if(equals(type.inward,"delivers"))}}|{{inwardissue.key}}|{{inwardissue.status.name}}|{{/}}
{{/}}

Kind regards,
Bill

[Alan Alder]

Thanks @Bill Sheboy  it's now put the record on the same row but different columns. Is there away to get them on different rows instead of columns

[Bill Sheboy]

Oops...missing a newline after the conditional to trigger the new row.  I updated the earlier post.

[Alan Alder]

@Bill Sheboy amazing thank you

[Alan Alder]

@Bill Sheboy if I wanted to show both delivers and depend on linked issues and then put the link type in the table how would I go about doing that?

[Bill Sheboy]

You could use the OR() conditional syntax, with two equals() calls, testing the different values.  Then add an additional column for the link type in the table.

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#or

[Alan Alder]

@Bill Sheboy sorry to be a pain I'm still having issues keep getting errors. The delivers is an inward type and the depends on is an outward type.

[Bill Sheboy]

The or() clause needs to wrap around the equals() tests for each type, as the equals() is what performs the test:

{{#if(or(equals(field, valueA), equals(field, valueB)))}}display when true{{/}}

Please note well: you are now mixing link directions in the expression, inward and outward links.  And so the logic to include the type, key, and status will need to be dynamic to use the correct one: inward versus outward.

I encourage you to experiment and get each type, "delivers" and "depends on", working separately and then try combining them.

[Alan Alder]

@Bill Sheboy  how do I add the dynamic elements as I'm still getting errors with everything I try

[Bill Sheboy]

Please post the expression you are trying.  That will help to diagnose what is happening.

As an alternative to the dynamic elements, you may instead repeat the conditional blocks inside of the iterator.

{{#issue.issuelinks}}
conditional block to test for "delivers", and add a row
conditional block to test for "depends on", and add a row
{{/}}

This will also handle the case of adding the same issue twice in case it has multiple links to the same issue, but with different types.

[Roberto Martignano]

Hello!
Thanks a lot for the support here, I was trying to configure a table field to display linked issues, and I found this article very helpful.

I only have one question:

- I would like to have a column that is edited manually, in order to manually add informations about the linked issues. Would it be possible to have that column "unedited" when the table is updated by the automation (i.e when a new issue is linked - the automation updates the table with the new issue, but keeping the manual data)?

Thanks a lot!

Roberto

[Bill Sheboy]

Hi @Roberto Martignano 

This is a very old thread, and so I recommend creating a new question with the "Ask a question" button at the top of the page...perhaps including a link to this thread for context.

When you create the new question, please include the following for context:

• what problem your rule is trying to solve; that is, "why do this?"
• your Jira version: Cloud, Server, or Data Center
• for Cloud, your project type
• an image of your complete rule, in a single image for continuity
• images of any relevant trigger, actions, conditions, or branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected, and why you believe that to be the case

Thanks!

Kind regards,
Bill