Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-24975

Text search for Parent Link field only matches on full tokens (words, issue keys)

      Summary

      When searching for issues in the Parent Link field on the create and edit issue screens, the search only matches entire words or the entire issue key.

      Environment

      • JIRA 7.4.1, Jira 7.11.2
      • JPO 2.4.0, JPO 2.26.0

      Steps to Reproduce

      1. Configure a new level in Portfolio Hierarchy Configuration
      2. Add the Parent Link field to the Create or Edit screen
      3. Create a new issue of the Issue Type configured for the new level
      4. Create or edit an epic and attempt to search for the issue created in step 3 in the Parent Link field

      Expected Results

      Partial text searches will match the issue. I.E. for an issue of TEST-1 This is a test parent issue, Typing "T" should match as would "p" or "par".

      Actual Results

      Partial text searches will not match the issue, only typing the entire word or issue will will match:

      For an issue of TEST-1 This is a test parent issue

      • "T" - No matches
      • "p" - No matches
      • "par" - No matches
      • "TEST-1" - Matches
      • "This" - Matches
      • "parent" - Matches

      Workaround

      Search using full words (tokens)

            [JSWSERVER-24975] Text search for Parent Link field only matches on full tokens (words, issue keys)

            Dear all,

            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            Any predictions for this item?

            Susete Eccher added a comment - Any predictions for this item?

            rafy0602 added a comment -

            This also affects Jira software 7.12.1 and Portfolio 3.2.0

            rafy0602 added a comment - This also affects Jira software 7.12.1 and Portfolio 3.2.0

            This also affects Jira Software 7.11.2 and Portfolio 2.26.0.

            It is inconsistent with other parts of Jira that users are expected to type the entire key in. For example, making a link in an issue starts to show matches so, when users don't see that behaviour with the Parent Link, they think something is wrong and start raising support tickets ...

             

            Philip Colmer added a comment - This also affects Jira Software 7.11.2 and Portfolio 2.26.0. It is inconsistent with other parts of Jira that users are expected to type the entire key in. For example, making a link in an issue starts to show matches so, when users don't see that behaviour with the Parent Link, they think something is wrong and start raising support tickets ...  

            Any news on this, any work-around ? It's an annoying behavior for our users. 

            Thanks in advance

            Morgan Wattiez added a comment - Any news on this, any work-around ? It's an annoying behavior for our users.  Thanks in advance

              Unassigned Unassigned
              dmcmorris@atlassian.com Douglas McMorris (Inactive)
              Affected customers:
              21 This affects my team
              Watchers:
              34 Start watching this issue

                Created:
                Updated: