NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Please see the attached screenshot. When issue searching is switched to advanced the search box is compacted to the size of the issue key column. Also the 'syntax help' option overlays the top field name in the search list if it's long enough.

      Workaround

      You can temporarily fix this via injecting css into your browser by stylebot or equivalent

      .query-component.navigator-search .search-container[data-mode="advanced"] {
        width:100%;
      }
      .query-component.navigator-search .search-container[data-mode="advanced"] .search-options-container {
        width:1%;
      }
      

            [JRASERVER-35519] Advanced JQL search box is compacted

            Problem resolved itself....

            Jaala Baldwin added a comment - Problem resolved itself....

            Advanced JQL field too narrow for use

            Jaala Baldwin added a comment - Advanced JQL field too narrow for use

            Fixed but broken again - see XWORK-115. Can't find corresponding JIRA issue.
            I have the same issue. Screenshot attached.

            Jaala Baldwin added a comment - Fixed but broken again - see XWORK-115. Can't find corresponding JIRA issue. I have the same issue. Screenshot attached.

            Hi Everyone,

            Thanks for your comments and patience on this issue. A fix was deployed to all OnDemand instances last night, Sydney time.

            We have confirmed that it has resolved the issue, and so have the above comments.

            Thanks again
            Josh

            Josh Devenny added a comment - Hi Everyone, Thanks for your comments and patience on this issue. A fix was deployed to all OnDemand instances last night, Sydney time. We have confirmed that it has resolved the issue, and so have the above comments. Thanks again Josh

            Working here too.

            Tom Bartolucci added a comment - Working here too.

            Search box and list/detail view work fine now, thanks!

            wilhelm otnes added a comment - Search box and list/detail view work fine now, thanks!

            Also working for me again!

            Toomas Romer added a comment - Also working for me again!

            Search box looks normal again. Still in process or confirmed resolved?

            Art Ignacio added a comment - Search box looks normal again. Still in process or confirmed resolved?

            Yes the switch between list/detail view will also be fixed.

            frother (Inactive) added a comment - Yes the switch between list/detail view will also be fixed.

            Great! Will the coming fix also provide the dropdown button to switch between "list view" and "detail view" again, this has disappeared from the GUI a couple of days ago?

            wilhelm otnes added a comment - Great! Will the coming fix also provide the dropdown button to switch between "list view" and "detail view" again, this has disappeared from the GUI a couple of days ago?

            Thanks for your continued patience, we plan to have the fix deployed within the next 8 hours.

            frother (Inactive) added a comment - Thanks for your continued patience, we plan to have the fix deployed within the next 8 hours.

            Hearing the same complaints from my users as well. Any ETA on when we might see this fixed ?

            Brian McGinnis added a comment - Hearing the same complaints from my users as well. Any ETA on when we might see this fixed ?

            Same problem here.

            Tom Bartolucci added a comment - Same problem here.

            Experiencing the same issue over here. Really tough to work with queries.

            Toomas Romer added a comment - Experiencing the same issue over here. Really tough to work with queries.

            Any update on this? Still seeing small search box. Thanks,

            Art Ignacio added a comment - Any update on this? Still seeing small search box. Thanks,

            All,

            Thanks for your patience on this issue. We're actively working on a deployment and will keep you updated on any further details.

            Cheers
            Josh

            Josh Devenny added a comment - All, Thanks for your patience on this issue. We're actively working on a deployment and will keep you updated on any further details. Cheers Josh

            frother (Inactive) added a comment - - edited

            This is caused by incompatibilities between the issue-nav-components & issue-nav-plugin versions. When service desk is installed it bundles issue-nav-components so will upgrade the version bundled with JIRA.

            In this case issue-nav-components has been bumped from 6.1.10 to 6.2.12, there is a change in this version bump that move styles from issue-nav-components into issue-nav-plugin. As issue-nav-plugin isn't upgraded with service desk these instances do not receive the styles that have been moved. Resulting in the bug.

            The css styles these instance are missing are below. They could be applied by stylebot while this issue is being resolved.

            .query-component.navigator-search .search-container[data-mode="advanced"] {
              width:100%;
            }
            .query-component.navigator-search .search-container[data-mode="advanced"] .search-options-container {
              width:1%;
            }
            

            Note: Service Desk 1.0.3 has resolved this issue. So the fix will likely be to upgrade the plugin.

            frother (Inactive) added a comment - - edited This is caused by incompatibilities between the issue-nav-components & issue-nav-plugin versions. When service desk is installed it bundles issue-nav-components so will upgrade the version bundled with JIRA. In this case issue-nav-components has been bumped from 6.1.10 to 6.2.12, there is a change in this version bump that move styles from issue-nav-components into issue-nav-plugin. As issue-nav-plugin isn't upgraded with service desk these instances do not receive the styles that have been moved. Resulting in the bug. The css styles these instance are missing are below. They could be applied by stylebot while this issue is being resolved. .query-component.navigator-search .search-container[data-mode= "advanced" ] { width:100%; } .query-component.navigator-search .search-container[data-mode= "advanced" ] .search-options-container { width:1%; } Note: Service Desk 1.0.3 has resolved this issue. So the fix will likely be to upgrade the plugin.

            Our team is experiencing same issue - I logged ticket too; I agree with others.
            This is wasting a lot of time and must be fixed soonest.

            Sharon Dobson added a comment - Our team is experiencing same issue - I logged ticket too; I agree with others. This is wasting a lot of time and must be fixed soonest.

            Same problem here. We have 200+ users loosing time with this. Please fix ASAP.

            Deleted Account (Inactive) added a comment - Same problem here. We have 200+ users loosing time with this. Please fix ASAP.

            Same problem. Very user-unfriendly! Would like this fixed asap please.

            John Thompson added a comment - Same problem. Very user-unfriendly! Would like this fixed asap please.

            It's been updated Shawn, thanks!

            Carlen Benard (Inactive) added a comment - It's been updated Shawn, thanks!

            Since the linked ticket was closed, please update the versions/labels on this one to include OD.

            Shawn Odegaard added a comment - Since the linked ticket was closed, please update the versions/labels on this one to include OD.

            Copying my comments from the linked ticket:

            This should not be marked as minor issue. If you have your view toggled to the preview one, you can't see any of the issues if you have a lengthy query, because there is no page scrollbar, just one in the results window.

            Additionally, there doesn't seem to be an option to toggle the view from preview to list unless you hit the 't' key, which the average user doesn't know how to do. Having it in the list view allows users to scroll down to see the issue numbers, but this is not a good workaround. This should be fixed immediately.

            I have gotten several complaints from users that this makes JIRA hard to use.

            Shawn Odegaard added a comment - Copying my comments from the linked ticket: This should not be marked as minor issue. If you have your view toggled to the preview one, you can't see any of the issues if you have a lengthy query, because there is no page scrollbar, just one in the results window. Additionally, there doesn't seem to be an option to toggle the view from preview to list unless you hit the 't' key, which the average user doesn't know how to do. Having it in the list view allows users to scroll down to see the issue numbers, but this is not a good workaround. This should be fixed immediately. I have gotten several complaints from users that this makes JIRA hard to use.

            Unacceptable. We, too are seeing this issue.

            Scott Berger added a comment - Unacceptable. We, too are seeing this issue.

            This is happening to us as well

            chris taylor added a comment - This is happening to us as well

            David Chan added a comment -

            We do not like this compacted view for the query

            David Chan added a comment - We do not like this compacted view for the query

              Unassigned Unassigned
              cbenard Carlen Benard (Inactive)
              Affected customers:
              39 This affects my team
              Watchers:
              45 Start watching this issue

                Created:
                Updated:
                Resolved: