We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-87667

When viewing an Advanced Roadmap plan, I want to be able to use Ctrl + F or Command + F to use the browsers search instead

    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      When pressing the keyboard shortcut of Command + F (mac) or Ctrl + F (windows/linux) supported web browsers will provide an search box to search for text on that page. However Advanced Roadmaps plans are intercepting this keyboard shortcut to instead use a search box that is built into the page.

      Suggested Solution

      It would be helpful to be able to disable this keyboard shortcut used by the page so that the browser search box could be used

      Why this is important

      This search box on the page is a means to optimize page loads. Since Advanced Roadmap plans can contain thousands of issues, to load the data for each on each time the page is loaded can cause a long load time. By not displaying all the issues on a plan when the page first loads, it can help with the performance of the site. Unfortunately, because of this design/optimization, the use of the browser's native search function is reduced. As there are situations where we known an issue exists on a plan, and we have loaded that plan fresh, but because it's in a collapsed section, the browser search cannot find it on that page. The existing in page search box is able to locate this, but customer desires to use the native browser search functionality to locate this instead.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Platform Cloud'
            1. Jira Platform Cloud
            2. JRACLOUD-87667

            When viewing an Advanced Roadmap plan, I want to be able to use Ctrl + F or Command + F to use the browsers search instead

              • 1
              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                Problem Definition

                When pressing the keyboard shortcut of Command + F (mac) or Ctrl + F (windows/linux) supported web browsers will provide an search box to search for text on that page. However Advanced Roadmaps plans are intercepting this keyboard shortcut to instead use a search box that is built into the page.

                Suggested Solution

                It would be helpful to be able to disable this keyboard shortcut used by the page so that the browser search box could be used

                Why this is important

                This search box on the page is a means to optimize page loads. Since Advanced Roadmap plans can contain thousands of issues, to load the data for each on each time the page is loaded can cause a long load time. By not displaying all the issues on a plan when the page first loads, it can help with the performance of the site. Unfortunately, because of this design/optimization, the use of the browser's native search function is reduced. As there are situations where we known an issue exists on a plan, and we have loaded that plan fresh, but because it's in a collapsed section, the browser search cannot find it on that page. The existing in page search box is able to locate this, but customer desires to use the native browser search functionality to locate this instead.

                        Unassigned Unassigned
                        aheinzer Andy Heinzer
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            aheinzer Andy Heinzer
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            2 Start watching this issue

                              Created:
                              Updated:
                              Resolved: