JQL Search for Team does not Recognize Team Names

XMLWordPrintable

    • 238
    • 38

      NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding suggestion.

      -- 

      Update as of 23rd October 2025

      Hi all,

      I'm April and I'm a product manager in Teams App. We're excited to announce that this is currently in progress - we're displaying a lozenge for teams in JQL. This will be available to customers by the end of the year. 

      I will update here once it's available. Let me know if you have any questions. 

      Problem

      Currently when JQL searching with the "Team" field, it only recognizes the team ID values. When using the actual Team names, no results are returned.

      Steps to Reproduce
      1. Create a shared team in JPO (i.e. red)
      2. Create a plan with issues and assign issues to the "red" team
      3. Commit the changes
      4. Now do an issue navigator search for:
        team = red
      • note that no results are returned
      1. Now do an issue navigator search for the ID, let's say the ID is "1":
        team = 1
      • note that results show the issues assigned to the team

      Extra Checks:

      Database confirms that the "red" team ID is 1:

      jira724=# select * from "AO_82B313_TEAM";
      AVATAR_URL | ID | SHAREABLE | TITLE
      --------------------------------------------------+----+-----------+----------------
      | 1 | t | red
      | 2 | t | blue
      /secure/projectavatar?size=medium&avatarId=10324 | 3 | f | SSP board Team
      (3 rows)
      Expected Behaviour

      JQL searches recognize both the team ID and team name as search parameters.

      Actual Behaviour

      JQL search only recognizes the team ID as a parameter

            Assignee:
            April Chi
            Reporter:
            David Chan
            Votes:
            212 Vote for this issue
            Watchers:
            103 Start watching this issue

              Created:
              Updated:
              Resolved: