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 rule for similar issues: what's wrong?

Dolores Rhyme

The use case is to link similar issues within a project. The rule needs to check 'similarity' when new issue is created.

It seems like a really simple one, but it doesn't work, issues are not linked:

To test the rule I pick any ticket in the project and create the same with slight modifications or without them at all to increase the chances of 'similarity', but Audit log says:

What do I do wrong?

Accepted answers

Nanda_v8ovge

We had a bug recently with a Similar issue description not working for JSM and it was fixed yesterday - https://jira.atlassian.com/browse/AUTO-902.

It should work for JSM now and as @Jack Brickey stated it is only JSM issues. It is still not implemented for Jira software project issues. Hence, it doesn't work on Jira issues.

All comments

Jack Brickey

hi @Dolores Rhyme ,

I may be mistaken but I think similar issues only works in JSM projects. I will research a bit. Can you test in JSM if you have it?

Dolores Rhyme

Thank you @Jack Brickey for a quick response. I'll check that and get back. You're an expert here, maybe you saw something to address this case for Jira Software? I'll truly grateful for this.

Jack Brickey

I am really not sure how you could do this with automation. It really take a good AI engine to identify "similar". If the issues had the same Summary maybe you could save the new issue Summary into a variable (newSummary) and use in a JQL ~ "{{newSummary}}". but I don't see this working TBH.

FWIW, here is an old post on Similar requests I posted a couple of years back - Similar-requests-what-do-you-guys-think-about-this

Dolores Rhyme

@Jack Brickey

I've checked the same settings for JSM but Audit log says the same. Interestingly: I've enabled the Similar issues feature in JSM, and it finds the same issues, but he ruke - doesn't.

I miss something in settings I suppose...

Nanda_v8ovge

We had a bug recently with a Similar issue description not working for JSM and it was fixed yesterday - https://jira.atlassian.com/browse/AUTO-902.

It should work for JSM now and as @Jack Brickey stated it is only JSM issues. It is still not implemented for Jira software project issues. Hence, it doesn't work on Jira issues.

Bill Sheboy

Thanks for that update, @Nanda

Do you know why that branch type is listed for rules in Jira Software projects, even when JSM is not installed?

Kind regards,
Bill

Nanda_v8ovge

I suspect that initially there was a plan to introduce this to Jira Software as well and then it must have been deprioritised.

I have requested to remove the components which are not compatible with JSW projects from the list in Automation section of Software projects.

Also created a feature request for this to be implemented in JSW projects - https://jira.atlassian.com/browse/AUTO-904

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation