how can I make JIRA search and display similar issues when create new issue?

[SherryX]

when I create an issue and enter some text (e.g. upgrade) in summary field within Atlassian support, some issues related to "upgrade" then display on the screen.

How can I make this happen in our JIRA? Our jira (5.1.8) does not search and display any related issues when users enter text in Summary field. This function can remind users that similar issues existed and also the solution may be there too. Thanks

[Renjith Pillai · Accepted solution]

Or use this plugin https://marketplace.atlassian.com/plugins/com.suggestimate

[hrzadnn]

Hi, maybe you guys still need the solution for your problem.. Here is what I found:

https://marketplace.atlassian.com/plugins/com.deniz.jira.similarissues

• customizable
• for 100 Users just $30! Amazing!

FYI: I dont work for them, I just think that those plugin is awesome and of course very helpful

Cheers,

Hariz

[Deniz Oğuz]

You can also use this plugin: https://marketplace.atlassian.com/plugins/com.deniz.jira.similarissues It is a new and customizable. In addition to suggesting similar issues in issue create dialog it also adds a similar issues tab that makes detection of duplicates easier.

[David Chan]

Hi Sherry,

That is actually from a custom script that is added to the Summary field's description. We call this script "Virgil", which can be found/downloaded from here:

• https://confluence.atlassian.com/display/Support/How+Atlassian+Uses+JIRA+for+Support%2C+Part+V+-+Additional+Questions
• direct link: https://confluence.atlassian.com/download/attachments/232554528/Virgil.xml?version=2&modificationDate=1312193802465&api=v2

You can also get more information about how we use JIRA for support here:

• https://confluence.atlassian.com/display/Support/How+Atlassian+Uses+JIRA+for+Support
• this is outdated, but does contain some good information

[SherryX]

thanks, David.

Do I just copy the xml script and paste to the Summary field's description?

Thanks for your help.

[David Chan]

Just ran a quick test, it seems that this may no longer work with the latest versions of JIRA. So this article is indeed outdated. In this case, it may be easier to follow @Renjith's suggestion with the plugin.