Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42645

Search in Jenkins should be case insensitive by default

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Component/s: core
    • Labels:
      None
    • Environment:
      Jenkins 2.49
    • Similar Issues:

      Description

      As discussed on the mailing list [1] there seems to be consensus that case insensitive search in Jenkins is much more intuitive. This unfortunately is an opposite to the situation available in Jenkins as of this issue creation [2]. In a context of changes in JENKINS-40718 (and the same approach in other places) it would be no longer possible to find FAILED jobs just by typing "fail" ("FAIL" would be required). This is counterproductive and misleading.

      This issue assumes change the default behavior for newly crated users and for an anonymous user.

      In addition it would be good to consider (probably as a separate issue to do not postpone the main action) a possibility to change that behavior for users that haven't intentionally opt-in to have case sensitive search. Unfortunately it can be impossible to determine that situation. Therefore maybe it would be beneficial (to prevent a "regression" related to JENKINS-40718 and similar changes) to reset that behavior and require from an user to opt-in to it once more - however, it could be somehow clumsy in the implementation (e.g. two values in XML for the same feature). Suggestions for that are welcome.

       

        Attachments

          Activity

          emszpak Marcin Zajączkowski created issue -
          emszpak Marcin Zajączkowski made changes -
          Field Original Value New Value
          Description As [discussed|https://groups.google.com/d/topic/jenkinsci-dev/I9PVV3j0Eb8/discussion] on the mailing list [1] there seems to be consensus that case insensitive search in Jenkins is much more intuitive. This unfortunately is an opposite to the situation [available|https://github.com/jenkinsci/jenkins/blob/76b5ba7f4641102917d551764e275f3d6044186e/core/src/main/java/hudson/search/UserSearchProperty.java#L28-L29] in Jenkins as of this issue creation [2]. In a context of [changes|https://github.com/jenkinsci/jenkins/pull/2683#issuecomment-275952138] in JENKINS-40718 (and the same approach in other places) it would be no longer possible to find FAILED jobs just by typing "fail" ("FAIL" would be required). This is counterproductive and misleading.

          This issue assumes change the default behavior for newly crated users and for an anonymous user.

          In addition it would be good to consider (probably as a separate issue) a possibility to change that behavior for users that haven't intentionally opt-in to have case sensitive search. Unfortunately it can be impossible to determine that situation. Therefore maybe it would be beneficial (to prevent a "regression" related to JENKINS-40718 and similar changes) to reset that behavior and require from an user to opt-in to it once more - however, it could be somehow clumsy in the implementation (e.g. two values in XML for the same feature). Suggestions for that are welcome.

           
          As [discussed|https://groups.google.com/d/topic/jenkinsci-dev/I9PVV3j0Eb8/discussion] on the mailing list [1] there seems to be consensus that case insensitive search in Jenkins is much more intuitive. This unfortunately is an opposite to the situation [available|https://github.com/jenkinsci/jenkins/blob/76b5ba7f4641102917d551764e275f3d6044186e/core/src/main/java/hudson/search/UserSearchProperty.java#L28-L29] in Jenkins as of this issue creation [2]. In a context of [changes|https://github.com/jenkinsci/jenkins/pull/2683#issuecomment-275952138] in JENKINS-40718 (and the same approach in other places) it would be no longer possible to find FAILED jobs just by typing "fail" ("FAIL" would be required). This is counterproductive and misleading.

          This issue assumes change the default behavior for newly crated users and for an anonymous user.

          In addition it would be good to consider (probably as a separate issue to do not postpone the main action) a possibility to change that behavior for users that haven't intentionally opt-in to have case sensitive search. Unfortunately it can be impossible to determine that situation. Therefore maybe it would be beneficial (to prevent a "regression" related to JENKINS-40718 and similar changes) to reset that behavior and require from an user to opt-in to it once more - however, it could be somehow clumsy in the implementation (e.g. two values in XML for the same feature). Suggestions for that are welcome.

           
          emszpak Marcin Zajączkowski made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Done [ 10000 ]
          emszpak Marcin Zajączkowski made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          emszpak Marcin Zajączkowski made changes -
          Environment Jenkikns 2.49 Jenkins 2.49
          emszpak Marcin Zajączkowski made changes -
          Resolution Done [ 10000 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          emszpak Marcin Zajączkowski made changes -
          Status Reopened [ 4 ] In Progress [ 3 ]
          emszpak Marcin Zajączkowski made changes -
          Status In Progress [ 3 ] In Review [ 10005 ]
          emszpak Marcin Zajączkowski made changes -
          Status In Review [ 10005 ] Resolved [ 5 ]
          Resolution Done [ 10000 ]

            People

            • Assignee:
              emszpak Marcin Zajączkowski
              Reporter:
              emszpak Marcin Zajączkowski
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: