Need to create an automation that detects if another ticket has the same page URL

Question

Objective:

We need to set up an automated process in Jira to detect tickets containing the same URLs as this causes authoring overlap. The goal is to check if a newly created issue shares same URLs with an existing issue that is not yet completed. If a match is found, a notification should be sent and the issue should be moved to “Blocked” status.

This is basically to prevent people working on the same page in different tickets.

We he tried setting this up but unfortunatelly we can’t make it work. We tried creating a custom field called "Page URL" that can hold several values and tried the below automation:

Current Setup:

1. Trigger: Issue Created.
2: JQL Condition: "Page URL" ~ {{issue.fields.customfield_57501 AND statusCategory != Done AND key != issue.key}}

Action: Send an email to xx@xx.com when a duplicate is found and move ticket to Blocked status.

Issues Encountered:

* The JQL condition is not working due to errors related to smart values in Automation.
* We tried wrapping the smart value in double quotes ("{{issue.fields.customfield_57501"}}), but it still failed.
* Jira does not allow validation of smart values in JQL, making troubleshooting harder.
* No access to the Audit Log makes it difficult to debug.
* If "Page URL" is a multi-value field, the ~ operator might not work correctly.
* Jira does not allow looping through multiple values in a single JQL query using Automation.

Any ideas why this is not working? Open to suggestions on other ways to make this work, doesn't need use the field we created if another solution is more appropriate.

Andreas Marinou · Answer

Hi @Harrison Ponce

We are maintaining the content for a client's website using AEM CMS.

The client creates a ticket describing the content update they need for the website and in that ticket they share the page URLs of the website pages they want to update.

Our team consists of 4 content editors and there's at least 5 different people creating tickets form client's side. This means a lot of the times some updates on pages overlap and we end up with 2 or more editors working on the same page. So the main aim is to avoid this overlap.

So when i refer to pages and URLs i mean the website's page URLs that the client provides in those tickets. At the moment, they provide these in the description of the ticket and most of the times there are more than 1 page URLs in a ticket.

Harrison Ponce · Answer

Hi @Andreas Marinou ! Interesting use case here. Can you provide some more context around what work you're doing with pages? Are these Confluence pages? Where is the URL stored today? Is it always one per issue?