-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Customer wishes to have an option or property in which the default behavior of JIRA's operator in the search bar can be changed from 'OR' to 'AND' so that you don't need to manually specify 'OR' each time in a search.
Customers comments (originally sourced from JSP-17318 and also JRA-5930).
You have to keep in mind that people are now used to using a "google like" ability and while the arguments made on issue
JRA-5930are okay I don't think they are solid enough to justify ignoring the issue.Since confluence is using the AND by default, then why not be consistent. I believe that is what Atlasssian is now pushing with your new JIRA studio. The fact that it is a uniform platform. If you want your platform to be uniform then what could be more important than having a uniform way of searching for stuff regardless of which product I am using?
If you guys are really worried about affecting existing users that are used to the OR default, then give me a system parameter that I can set based on my preference. Then this would make everyone happy.
- is cloned from
-
JRASERVER-5930 Default search operator should be AND, not OR
- Closed
- relates to
-
JRACLOUD-14216 switchable option between default boolean 'AND' and 'OR' operators in search
- Closed
Hi,
This is a bulk update to specific issues in the JIRA (JRA) project
As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.
Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com
If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.
Best regards
Josh Devenny and Roy Krishna
JIRA Product Management