Robert G. Nadon Expert

I believe the only answer is to access the database directly. Closing this one out.

The problem was a plugin. Safe mode the problem disappears. I removed the plugins we were no longer using left safe mode and all is happy again. Thanks all!

No that's not it. Thanks though.

It says this: JIRA Software 7.2.6 500 users (417 used) You are 83 users away from the maximum allowed by your license. Manage existing usersMaintenance expires 07/06/17Support entitlement number (SEN)SEN-XXXXXXX <not showing this to public>License typeCommercialOrganisation nameVerdasysLicense keyAAABmg0... Looks good to…

It should be as we have a good Agile license and a good JIRA license on 6.4.7, but how do I tell?

I never use IE for anything except playtime. For business, I primarily use Chrome and if that fails then I will switch to Firefox. Our problem was not a browser one. I think crucible was doing something though, but a top showed it was the only thing consuming CPU and memory and was not consuming very much of either. If…

Perforce (moving to GitHub later this year but currently using Perforce). It self corrected, and so is not so critical, but I still would like to know if there was a profiler for me to do some analysis.

Actually it does WOW thanks Learnt something knew issueFunction in hasLinks('duplicates') 

Can you use that in a JQL filter? Above I have the Script runner validator code already. I need to create a filter to find anyone who has created a link as Duplicate yet did not close the issue.

Ugh JQL tricks is not free bummer. Anyone know how to find all issues that have a duplicate link? I bet I could with the CLI... hmm...

No ,but that is not what I need. I only need to: * Only allow a resolution to be closed with duplicate if you have an issue linked with duplicate. The code above. * prevent people from link with duplicate and not closing the issue For that one I will create a JQL query to find any non closed issues with a Duplicate link…

Actually JIRA does support it as of 4.4 and that is how we are doing it. (include Linked Issues on the closing screen to accomplish it) I was hoping to be able (I am sure I could if I knew js better) hide the link at all time except if I am on the closing screen. Though we have many teams using JIRA (Legal, Marketing, etc)…

But that would still allow an issue to have a duplicate link but not be closed. Even if I could have a filter that people could subscribe to that would have any issue that has a duplicate link and is not resolved that would work, but I prefer to prevent this behavior completely. So I do not want people to link as duplicate…

Ahh OK makes sense. Since we are standalone server and have a pretty secure firewall, I am not sure that this will affect us, but I will bring it to the management team and let them decide. Thanks!

Thank you, strange that it didn't have update in the manage plugins, but an uninstall and reinstall fix it. Thanks again!

I have submitted a bug to Atlassian https://support.atlassian.com/servicedesk/customer/portal/14/CSP-184536 

I am getting the same thing, and I am JIRA server. We just upgraded Confluence as well.

Thanks, I wish I could mark both as correct answers, but due to price I believe I will try the Similar Issues Finder plugin below. Thanks though!