New lookup issues fields

[#1]

Hi everyone!

Last year, we released a new component, Lookup Issues. This component allows users to use JQL to insert a list of issues into their rule by accessing the smart value {{lookupIssues}}. Up until now, these issues have been very limited in what fields are populated. We received a lot of feedback around including more fields on these issues, and we have now released an update which does just that. 

You can now access any field that you would normally be able to access on an issue smart value.

Why would you do that?

Those who are familiar with the lookup issues component know how useful it can be. Whenever you want to get a list of issue keys to include in a correspondence, do routine checks on a group of issues, or just get a count of issues matching a condition, lookup issues is the component to use.

However, we previously only allowed access to a basic subset of available fields. This limited the usability of the component. For example, if you wanted to access a custom field on a list of issues, this was not possible. Now, you have full access to all fields, including custom ones, so you can use them however you like in your rules.

How do you do that?

To use the lookup issues action, take a look at our documentation or have a read about it in its community article. The change in functionality means that the issues looked up by this action can be treated like any normal issue, so have a go with the smart values outlined in our documentation 

[W Bot]

Fantastic news, thanks to the Atlassian Automation for Jira Team for continuing to innovate an amazing product!

[Bill Sheboy]

This is awesome!  Thanks to you and the team, @Sam Harding !!

Does this close out this suggestion I made, or are there still some unavailable fields?

https://jira.atlassian.com/browse/JRACLOUD-75018

Kind regards,
Bill

[Curt Holley]

So I should be able to get custom date fields, is that right? @sam 

As I'm experimenting with such a field, but nothing is coming through. 

Using: {{issue.customfield_10298.fullDate}}

FYI, doesn't seem to matter which date format I try

[Sam Harding]

@Bill Sheboy It does! Just closed it out

Cheers
Sam

[Sam Harding]

@Curt Holley it should be able to get custom date fields. Can you verify the smart values {{issue}} and {{issue.customfield_10298}} to see whether the smart value structure is correct? I am not sure that the 'issue' part of that is correct in the context of using a lookupIssues smart value.

I would expect the smart value to be something like

{{#lookupIssues}}{{customfield_10298.fullDate}}{{/}}

Cheers
Sam

[Curt Holley]

Correct @Sam Harding working now I've made it {{customfield_10298.fullDate}}

Thanks for that.

This is a great enhancement of the Look-up issues action.

[Italo _Modus Create_]

That's awesome! It's great to see Automation for JIRA receiving new features.

The next feature I would like to see implemented is the following:

• JRACLOUD-77612 - Encrypt or Hash outgoing webhook headers

[Joshua Kochelek]

This is great!! I have so many use cases... Thank you for sharing @Sam Harding!

[Céline TAMBURRO]

Hello, is it available on Data Center ? Thanks.

[Gisela Lassahn]

Hi,

when will the lookup issue functionality be available for Jira Data Center?

Many thanks (for implementing it and for any answer to my question)!

Kind regards,

Gisela

[Stephan Maass]

Is it there for datacenter yet?

[Julien Rey]

@Stephan Maass 

The lookup functionality does not exist for Jira Data Center yet. 

There is a feature request ticket meant to implement this feature which is tracked in https://jira.atlassian.com/browse/JIRAAUTOSERVER-53.