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 Data Center'
  1. Jira Data Center
  2. JRASERVER-73922

Epic Link searchQuery is not returning all matching values

      Issue Summary

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Create an Issue
      2. Crate two Epics: Epic1 & Epic2
      3. Edit the Issue and try to add one of the Epics, start typing "Epic"

      Expected Results

      Expected behavior, locally tested in Jira version 8.17.0:

      Also, making a REST call, returns the expected values:

      <base-URL>/rest/greenhopper/1.0/epics?searchQuery=Epic&projectKey=AA&maxResults=100

      As it is shown, it seems that it was working as expected in old versions like 8.17.0

      Actual Results

      Faulty behavior:

      <base-URL>/rest/greenhopper/1.0/epics?searchQuery=Epic&projectKey=AA&maxResults=100

      Workaround

      Workaround 1

      Typing the full Epic Name will show the result:

      Workaround 2

      From our KB:
      Performance updates to Jira epic picker

      If you want to revert to the old mechanism, you need to enable the following dark feature: com.atlassian.jira.agile.darkfeature.legacy.epic.picker. For details, see How to manage dark features in Jira.

      1. In a web browser open URL : <BASE_URL>/secure/admin/SiteDarkFeatures!default.jspa
      2. To enable a feature flag, type com.atlassian.jira.agile.darkfeature.legacy.epic.picker.enabled in the Enable dark feature text area and click the Add button.
      3. Go to your Issue and check if it is showing any match when staring to type the Epic name.

            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 Data Center'
            1. Jira Data Center
            2. JRASERVER-73922

            Epic Link searchQuery is not returning all matching values

                Issue Summary

                This is reproducible on Data Center: yes

                Steps to Reproduce

                1. Create an Issue
                2. Crate two Epics: Epic1 & Epic2
                3. Edit the Issue and try to add one of the Epics, start typing "Epic"

                Expected Results

                Expected behavior, locally tested in Jira version 8.17.0:

                Also, making a REST call, returns the expected values:

                <base-URL>/rest/greenhopper/1.0/epics?searchQuery=Epic&projectKey=AA&maxResults=100

                As it is shown, it seems that it was working as expected in old versions like 8.17.0

                Actual Results

                Faulty behavior:

                <base-URL>/rest/greenhopper/1.0/epics?searchQuery=Epic&projectKey=AA&maxResults=100

                Workaround

                Workaround 1

                Typing the full Epic Name will show the result:

                Workaround 2

                From our KB:
                Performance updates to Jira epic picker

                If you want to revert to the old mechanism, you need to enable the following dark feature: com.atlassian.jira.agile.darkfeature.legacy.epic.picker. For details, see How to manage dark features in Jira.

                1. In a web browser open URL : <BASE_URL>/secure/admin/SiteDarkFeatures!default.jspa
                2. To enable a feature flag, type com.atlassian.jira.agile.darkfeature.legacy.epic.picker.enabled in the Enable dark feature text area and click the Add button.
                3. Go to your Issue and check if it is showing any match when staring to type the Epic name.

                        kcichy Kamil Cichy (Inactive)
                        458e633c07a6 Jose Antonio Uribe
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        7 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            kcichy Kamil Cichy (Inactive)
                            458e633c07a6 Jose Antonio Uribe
                            Affected customers:
                            1 This affects my team
                            Watchers:
                            7 Start watching this issue

                              Created:
                              Updated:
                              Resolved: