Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-73416

JQL issueLinkType has Unsupported Operators is and is not

      Summary

      In Jira Cloud the the JQL field referance for "issueLinkType" only supports the operators "=", "!=", "IN", "NOT IN" as covered in:

      However Currently the Unsupported operators "IS" & "IS NOT" are avaliable for use in the JQL options for advanced search, and when these unsupported link type operators are used they do not supply data that would be consistent with what would be expected per the input.

      Environment

      • Jira Cloud JQL Advanced Search

      Steps to Reproduce

      1. do an advanced search in an instance that has issues with and without linked issues
      2. use the following two JQL searches:
        issueLinkType is not EMPTY
        

        AND

        issueLinkType is EMPTY
        

      Expected Results

      Either the operators "IS" and "IS NOT" are not avaliable as they are noted as Unsupported operators

      OR

      Only issues without a linked issue will be returned when using "issueLinkType is EMPTY" AND Only issues with linked issue will be returned when using "issueLinkType is not EMPTY"

      Actual Results

      Each search will result in different sets of issues returned, and each result set will include both; field values with AND without a linked issues

      Notes

      The "IS" and "IS NOT" operator look to have been added to the JQL when fixing the following BUG:

      Workaround

      Option 1:

      • Do not use "IS" or "IS NOT" with "issueLinkType" as they are unsupported operators for the field type

      Option 2:

      • For similar behavior to what would be expected results of an "IS EMPTY" or "IS NOT EMPTY" you can use the workaround noted in JRACLOUD-72795 and do a filter "!=" referance to a saved filter to exclude any issue with the set list of link types, like the following:
      • Create a saved filter including a list of all the current link types EXE:
        saved filter = issueLinkType in ("all", "of", "the Issue Link Type Names", "as a comma separated", "List", "using Both the" "Outward Description" "And" "Inward Description")
        
      • Then in your final JQL:
        Project = EXE AND filter != <filter_ID>
        

            [JRACLOUD-73416] JQL issueLinkType has Unsupported Operators is and is not

            Atlassian Update - December 2022

            As per this comment I am closing this ticket.

            If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - December 2022 As per this comment I am closing this ticket. If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it.

            I believe this issue is a duplicate of JRACLOUD-73640 – JQL issueLinkType is inconsistent when using != or NOT IN operators

            I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone thinks both issues should continue to exist. Thank you!

            Anusha Rutnam added a comment - I believe this issue is a duplicate of JRACLOUD-73640 – JQL issueLinkType is inconsistent when using != or NOT IN operators I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone thinks both issues should continue to exist. Thank you!

            Thi has impacts on our way to contract with our customer. It is very hard to find the bug, and it took even 1 month to your Atlassian support to know and redirect me to the documentation explaining the workaround. Imagine if your own team doesn't know the workaround, how tough it is for a basic user !

            Florian Royer added a comment - Thi has impacts on our way to contract with our customer. It is very hard to find the bug, and it took even 1 month to your Atlassian support to know and redirect me to the documentation explaining the workaround. Imagine if your own team doesn't know the workaround, how tough it is for a basic user !

            Megha added a comment -
            Atlassian Update - January 27, 2021

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Megha added a comment - Atlassian Update - January 27, 2021 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              gcardoso@atlassian.com Gonçalo Cardoso
              emccutcheon Earl McCutcheon
              Affected customers:
              14 This affects my team
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: