Automation not setting the value of a Hyperlink field

[Peter James]

I've been playing with the new automation templates and have made a small edit to the 'When an idea is created -> create a corresponding confluence page' such that it updates a field on the same ticket to reference the page it has just created.

The audit log says that it has run correctly but the field does not get updated :(

I have tested the new rule component by instead adding a comment that holds the url and that works just fine.

Does not error but does not set the field value:

The field is a hyperlink field so does expect a valid url but my comment test does show it to be a valid value that I am trying to save

Any help would be appreciated.

[Jan-Hendrik Spieth · Accepted solution]

Yes, you can search for linked issues using the linkedIssues() function. The only catch is with the type of the link, because it seems the polaris link type "implements" cannot yet be used as a filter.

So for example:

issue in linkedIssues("IDEA-123")

This will return all issues that are linked to the idea, not only the delivery tickets. But maybe that still helps, already?

[Mirko Grahnert]

Thanks @Jan-Hendrik Spieth

This is helpful! The issue we have with this approach is that only tickets that are 'directly' linked to the idea show up as 'linked issues'. For example, if I link an epic to an idea, only the epic itself shows up as 'linked issue'. The child tickets that are linked to the epic however don't show up as linked to the idea. 

[Jeny Stoeva]

@Mirko Grahnert You can use the above suggestion to get the directly linked issues and linkedIssue in linkedIssues("IDEA-414") to get the linked issues and also the sub-tasks of those linked issues. This will return what you need.

[Mirko Grahnert]

Awesome, that @Jeny Stoeva

[David Laine]

I am having trouble with this - the links for the delivery tickets do not return from the JQL using linkedIssues in either of the above suggestions. 

All I want to do is return a list of the delivery tickets linked to an idea. Is this even possible or supported at the moment? Seems like a pretty regular/fundamental thing to want to do.

[Matt Lane]

I am also curious how you can just go ahead and query for ALL Jira issues that are delivery issues for ANY/ALL ideas in a Jira Discovery Project

[Jeny Stoeva]

Hi @David Laine ,

I just checked again using linkedIssue in linkedIssues("IDEA-414") does exactly what you want to achieve. It returns:

• The linked to the IDEA delivery tickets AND
• All Subtasks of those delivery tickets

It returns everything in essence.