Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-39275

Remove slow execution path on DefaultSearchRequestURLHandler

    XMLWordPrintable

Details

    • Severity 3 - Minor
    • Hide

      Atlassian Update – 04 July 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 04 July 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

    Description

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

      On DefaultSearchRequestURLHandler#handleRequest, there is an execution path that ends up calling getSearchRequestFactory().createFromParameters(null, loggedInUser, new ActionParamsImpl(parameters));.

      That createFromParameters method is deprecated on SearchRequestFactory because it's very slow since it ends up calculating the context for the given query.

      As we already know, calculating such context is an expensive operation that has a poor performance on large JIRA instances.

      Luckily, that execution path can be removed from DefaultSearchRequestURLHandler, since it is only reached when the jql string parameter is null. After investigation, we have come to the conclusion that the only way of getting a null jql parameter is if the user plays with that url and removes it.

      We should remove this execution path by handling the null case as if it was an empty jql string.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-39275 Remove slow execution path on DefaultSearchRequestURLHandler

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-39278 Investigate context calculation and subsequent filtering of navigable fields in JIRA

          • Closed

          Activity

            People

              Unassigned Unassigned
              jsanchez@atlassian.com Jose Jaime Sanchez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: