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

JQL function to display all issues linked by the linked issue's resolution

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • JQL
    • None
    • 0
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      As per JRASERVER-25640, there is now a JQL to search issues based on the issue link type. However, it is not possible to further refine the search by filtering the results based on the linked issues' resolution.

      Useful scenario:

      • A filter gadget is used to display all the issue the user can work on.
      • The filter is set to display all the issues that do not have linked issues with the type "block", as this is a blocker to the user.
      • Should the "block" linked issue has been resolved, the parent issue should be displayed in the filter gadget so that the user can work on it.

      Suggested Solution

      Introduce a JQL that can search based on the linked issue's resolution.

      Workaround

      Use third-party plugins. Refer to this Community discussion: How to compare the status of linked issues ?

            [JRASERVER-69124] JQL function to display all issues linked by the linked issue's resolution

            Richard Mann added a comment -

            Indeed. We were very disappointed when moving from Server to Cloud to find this feature that worked under Server (vis ScriptRunner) no longer worked in Cloud.

            Rather begs the question, why would we stay on Cloud as it is compromising our workflow.

            Richard Mann added a comment - Indeed. We were very disappointed when moving from Server to Cloud to find this feature that worked under Server (vis ScriptRunner) no longer worked in Cloud. Rather begs the question, why would we stay on Cloud as it is compromising our workflow.

            Simon Stockton added a comment -

            It was 8 years between when JRASERVER-25640 was created and when it got implemented. It is most unfortunate that the resolution of JRASERVER-25640 didn't go as far as allowing filtering of the status of linked issues, as is done in JQL and Scriptrunner.

            It is astonishing that providing a list of issues that a user can work on is not a standard feature of Jira and the expectation is to purchase additional plugins to achieve this basic functionality. Hopefully, it will not be another 8 years before this feature is added!

            Simon Stockton added a comment - It was 8 years between when  JRASERVER-25640  was created and when it got implemented. It is most unfortunate that the resolution of  JRASERVER-25640  didn't go as far as allowing filtering of the status of linked issues, as is done in JQL and Scriptrunner. It is astonishing that providing a list of issues that a user can work on is not a standard feature of Jira and the expectation is to purchase additional plugins to achieve this basic functionality. Hopefully, it will not be another 8 years before this feature is added!

              Unassigned Unassigned
              imazuki Irfan Mazli Mazuki (Inactive)
              Votes:
              38 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: