In JIRA (6.1 for me), Search for Issues (menu Issues) will first load all issues in the instance (most users have browse permission to all projects).
Why is this??
This is like to have a SQL client that loads first all rows in the database before actually specifying the query.
I have seen some feature request about this but they are open...
Anyone knows any workaround?
Thanks in advance.
This was debated earlier in one of the threads and even I am not really in favour of this behaviour - You can see that discussion here https://jira.atlassian.com/browse/JRA-30855
What I remember was that, the discussion went in these lines - as long as the performance is not a concern, why shouldn't it be loaded.
Do you know if Atlassian has some channel to handle this? a sort of customer advocate?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.