Force Summary to be unique on all new issues
Could you describe how to have the Summary field checked during the create step such that if any other issue within the project has the same summary creation is rejected?
Thanks
Comments (9)
-
repo owner -
reporter Thanks very much. Trying this out now.
-
reporter Is there a way to make this stricter?
It did work on my first test when the summary of the new issue was "Testing Vendor Logic" - I saw my own validation failed message. Nice!
Then I edited that summary to "Testing Vendor Logic - Success!"
Then I created a new issue with that same summary a few times. I have multiple issues with the same summary. Maybe because of the specials characters in the field "-" and "!" ?
EDIT: I also made sure that the Run As was set to a user without any restrictions to view the issues.
EDIT2: I tried thisJQL manually
EDIT3: I think it is the punctuation. Both fail: * project = AT AND Summary ~ "-" * project = AT AND Summary ~ "!"
Correct me if I'm wrong but I imagine there's little you can do about that. ?
-
reporter It's a limitation of Jira so this is actually just fine.
Cannot praise JWT enough. It's fantastic!
-
reporter - changed status to resolved
-
reporter - changed status to open
Hi Fidel,
Is there an alternative way to enforce unique summary names? This method disallows even similar names. eg, the summaries "cm_reaction_to_fire_anims" and "cm_reaction_on_fire_anims" clash. Many of our summaies will be really similar but unique.
I'm guessing this is because "summary = ..." is not allowed in JQL. Only "summary ~ ..."
Thanks
-
repo owner Hi @w_b,
Let's try using "Boolean validator with math, date-time or text-string terms" instead of "Validation on JQL Query". Use the following boolean expression:
count(filterByPredicate(issuesFromJQL("project = " + %{00018} + " AND summary ~ '" + %{00000} + "'"), %{00000} = ^%{00000})) = 0
I'm assuming that the JQL query you are using is:
project = %{00018} AND summary ~ '%{00000}'
-
reporter - changed status to resolved
That works! Thanks!
-
reporter - changed status to closed
- Log in to comment
Hi @w_b,
You have to use "Validation based on JQL query" validation with the following configuration:
JQL Query can be any of these ones:
1) Forbid an issue in same project and issue type with same summary.
2) Forbid an issue in same project with same summary.
where
%{00018}
is field code for Project key,%{00014}
for Issue type, and%{00000}
for Summary.