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

How to use LookupIssue to update a custom field

Adam Hasselgren

I created a new Jira issue type called "Customer". The purpose is to store information about specific customer as well as identify who the project manager is for one.

On "Customer" I have a couple fields

Customer (drop down ,single choice)
Project Manager (user lookup, single choice)

On our normal stories, bugs, etc it also have the same fields.

Today I have some automation where if the "Customer" field is updated on a normal Jira ticket, it automatically updates the "Project Manager" field based upon the "Customer" field. As of right now I have an automation script per project manager where I hard code customers (which works but not a good solution).

What I would like to do is have some automation where it can reference the new "Customer" artifact and lookup the project manager attached to a particular customer. In Excel terms I'm basically looking to do a vlookup on a customer record to pull across the PM for a particular ticket. I know I need to leverage the lookupissues function just can't get it to work. Not sure if it's an issue because I have the "Customer" artifact in another project or if that shouldn't impact it.

Here is the field information

"customfield_10109": "PM"
"customfield_10063": "Customer"

Project Information

Project A (all tickets)
Project B (test project where the customer artifact is located)

Accepted answers

Stefan Salzl_0i980g

Hi @Adam Hasselgren ,

How far did you come so far? Could you show your current automation rule? That would help the community to better understand the problem.

Best
Stefan

All comments

Stefan Salzl_0i980g

Hi @Adam Hasselgren ,

How far did you come so far? Could you show your current automation rule? That would help the community to better understand the problem.

Best
Stefan

Adam Hasselgren

I'm sure I'm missing something but I did verify the customer had an entry in the ticket that matched on the "Customer" artifact.

Stefan Salzl_0i980g

Hi @Adam Hasselgren ,

First thing: smart values are case sensitive. So try to change to {{lookupIssues...}} (capital „i“) in your esit action.

furthermore (as the field is still a list) could you try the following in your edit action:

see the documentation below:
https://support.atlassian.com/cloud-automation/docs/examples-of-using-smart-values-with-lists/

Please let me know if this works.

Best
Stefan

Adam Hasselgren

Still no luck..I've included all the screenshots from each part of the automation just in case I'm completely missing something

Pierre Allard

Hello,

I'm trying to implement the same kind of logic but it seems I'm not able to retrieve

my custom field from my lookupIssue to put it in the audit log.

Here's the automation details:

Here's the audit log:

I've no error, the rule is a success...

I've tried with and without .value but it's never working.

Any idea ?

My custom field is a URL, could it be due to a known limitation with this kind of field ?

Thanks in advance for your help !

Welcome!

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

Quick Links

Find more posts tagged with

automation