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

Automation: Field values identical to same field value in another issue

Johannes Nyberg

Hello Atlassian!

I´m trying to setup a process to handle all of our faulty Hardware with our Jira-Service-Desk. This require our customer to answer questions such as:

- Serial Number of the product

- Error description

- Any troubleshooting done?

What I would like to do is to setup up an automation that monitors if an issue is created, it will check if that specific serial number already has been reported as faulty.

Would be enough to send an email saying that this piece of HW has already been faulty.

All the best,
Johannes Nyberg

Accepted answers

Matthias Gaiser _K15t_

Hi @Johannes Nyberg

yes, you can achieve something like this with Automation.

I thought of an automation like this:

When: Issue Created
Then: Lookup issues
- You can specify a JQL then to look for the issues, you're interested in. If you're value is stored in the custom field 11127, you could use a JQL like this:
```
cf[11127] ~ {{issue.customfield_11127}} and key != {{issue.key}}
```
And: Add comment to issue
- In the comment, you can use {{lookupIssues}} in order to include your result.
  You could probably modify that with an if condition that the comment is only written if there actually are some issues.

For more details, I'd recommend to check out the docs about smart values or the lookupIssues function.

I hope that helps,
Matthias.

All comments

Alex Koxaras -Relational-

Hi @Johannes Nyberg ,

So let me get this straight:

the user will enter the serial number when creating the ticket
The ticket will be raised, even if the serial number already exists
There will be an automatic email send out to the customer about "Getting the request"
There will be a second email notifying the customer that this serial number already exists and has reported as faulty.

Are the above correct? If yes, then I would say that this can be done, but I strongly disagree about sending a second email to the user. I would either auto-comment his/her request and automatically move this issue to Done, or just auto-comment and wait from the customer's reply.

With that said, this can be done by Jira Automation and lookupissues of within the workflow. Do you have any apps installed on your instance?

Alex

Matthias Gaiser _K15t_

Hi @Johannes Nyberg

yes, you can achieve something like this with Automation.

I thought of an automation like this:

When: Issue Created
Then: Lookup issues
- You can specify a JQL then to look for the issues, you're interested in. If you're value is stored in the custom field 11127, you could use a JQL like this:
```
cf[11127] ~ {{issue.customfield_11127}} and key != {{issue.key}}
```
And: Add comment to issue
- In the comment, you can use {{lookupIssues}} in order to include your result.
  You could probably modify that with an if condition that the comment is only written if there actually are some issues.

For more details, I'd recommend to check out the docs about smart values or the lookupIssues function.

I hope that helps,
Matthias.

Johannes Nyberg

Thanks for your quick reply Alex.

1. Yes, it is mandatory for the ticket to be raised.

2. Yes, the ticket will always be raised independently of it has been faulty or not before.

3. The purpose is to notify us internally saying that this item has already been repaired.

So the process will be same regardless of if the HW has been repaired earlier or not. The purpose is only to give us a heads-up with this information.

Johannes

Johannes Nyberg

Awesome! Tested and it works. Thank you Matthias and have a good day.

Johannes Nyberg

As you mentioned it is possible to add an if-statement to make sure that the comment is only done when the list is not equal to empty.

Marc Isikoff_o8qjap

We have Jira server working in our firm's cloud environment; does this solution still work?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management