Hi Our customers can send a request to have their software updated by us. Each such process includes a manual collection of software fixes that are available for that particular customer. Would the following be possible: * For each "Update or upgrade" issue that is being created * Take the value of the Organisation or Company name (custom field) * Look for issues containing that Organisation or Company name that are also in the status "Ready to be delivered" * And Link these issues to the created "Update or upgrade" issue This way agents will not need to go through dashboards or issue lists to manually link eligible issues. The main issue for me is finding a proper method to compare issues and based on this comparison trigger the link action.

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

Advanced compare automation with links

Jarosław Kaczmarek

Hi

Our customers can send a request to have their software updated by us. Each such process includes a manual collection of software fixes that are available for that particular customer.

Would the following be possible:

For each "Update or upgrade" issue that is being created
Take the value of the Organisation or Company name (custom field)
Look for issues containing that Organisation or Company name that are also in the status "Ready to be delivered"
And Link these issues to the created "Update or upgrade" issue

This way agents will not need to go through dashboards or issue lists to manually link eligible issues. The main issue for me is finding a proper method to compare issues and based on this comparison trigger the link action.

Accepted answers

Fernando Eugênio da Silva

@Jarosław Kaczmarek

Yes, this is possible using automation's Lookup Issues feature.

In short, it will collect an existing Jira base and fill in a certain value.

The most practical and functional example in your case would be using Organizations, but it can work with customfield as well.

See the automation example you must follow to make this work.

Bring this for your scenario

Trigger: Issue created

Condition: Issuetype or Request type "Update or upgrade" in your case;

ACTION: lookup Issues > then insert JQL like: Organizations = XXXX AND status = XXXXX

Then after lookup issues you need add one more action "Link issue". And configure like this:

Choice the type from linked issues and in the next colummn insert the smartvalue {{lookupIssues}}.

This way Jira will hyperlink all the issues filled in within the lookup you applied in the previous action.

Hope this helps you.

If you have any questions, let me know

All comments

Fernando Eugênio da Silva

@Jarosław Kaczmarek

Yes, this is possible using automation's Lookup Issues feature.

In short, it will collect an existing Jira base and fill in a certain value.

The most practical and functional example in your case would be using Organizations, but it can work with customfield as well.

See the automation example you must follow to make this work.

Bring this for your scenario

Trigger: Issue created

Condition: Issuetype or Request type "Update or upgrade" in your case;

ACTION: lookup Issues > then insert JQL like: Organizations = XXXX AND status = XXXXX

Then after lookup issues you need add one more action "Link issue". And configure like this:

Choice the type from linked issues and in the next colummn insert the smartvalue {{lookupIssues}}.

This way Jira will hyperlink all the issues filled in within the lookup you applied in the previous action.

Hope this helps you.

If you have any questions, let me know

Jarosław Kaczmarek

Hi @Fernando Eugênio da Silva

Thanks for your help It works already but I added to the smart value the key component (i.e. {{lookupIssues.key}}.

Now, will it be possible to go by without specifying the Organization in the first place? We have like 60 different orgs that may want to have their software updated and creating 60 iterations of the same rule sounds crazy

Is there a built-in method that recognizes on its own the Organization of the issue reporter and then based on this runs the lookup? Sort of: get the value of Organizations and then lookup for that value

Fernando Eugênio da Silva

@Jarosław Kaczmarek

Yeah, hahaha I thought about that too about you having too many organizations and it creates a problem with too many automations.

JQL feature doesn't allow to filter Organizations like this:
Organizations = currentUser()

It also doesn't allow identifying the value per user this way: Organizations in currentUser()

So I really believe that natively you'll need to create a lot of automation rules to make this work well without associating various items from other organizations and getting everything mixed up.

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