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: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-1695

Portfolio Team field has limited access from JQL within JIRA

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

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

      JPO-66 had introduced mapping the "team" field to JIRA. This is fantastic. However, JQL only allows "=" and "in" operators. They also don't accept EMPTY or NULL.

      Also, getting this value in any scripting plug-in such as issue.get(“Team”) returns com.atlassian.jpo.team.data.DefaultTeam. This latter class is not exposed yet in the JIRA API.

      The request is to be able to query this field for the scrum board filter for any issues that don't have a team assigned. i.e. "project = XYZ and Team = EMPTY". Alternatively, if the NULL/EMPTY value can't be returned, this could be written as "project = XYZ and Team not in (TeamA, TeamB, TeamC)".

      Can this enhancement be considered or please indicate if there is a current workaround.

      Thanks

            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: 'Advanced Roadmaps'
            1. Advanced Roadmaps
            2. JPOSERVER-1695

            Portfolio Team field has limited access from JQL within JIRA

            This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

              • JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

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

                JPO-66 had introduced mapping the "team" field to JIRA. This is fantastic. However, JQL only allows "=" and "in" operators. They also don't accept EMPTY or NULL.

                Also, getting this value in any scripting plug-in such as issue.get(“Team”) returns com.atlassian.jpo.team.data.DefaultTeam. This latter class is not exposed yet in the JIRA API.

                The request is to be able to query this field for the scrum board filter for any issues that don't have a team assigned. i.e. "project = XYZ and Team = EMPTY". Alternatively, if the NULL/EMPTY value can't be returned, this could be written as "project = XYZ and Team not in (TeamA, TeamB, TeamC)".

                Can this enhancement be considered or please indicate if there is a current workaround.

                Thanks

                        Unassigned Unassigned
                        ab03bb162159 Michael Howard
                        Archiver:
                        atibrewal@atlassian.com Aakrity Tibrewal

                          Created:
                          Updated:
                          Resolved:
                          Archived:

                            Unassigned Unassigned
                            ab03bb162159 Michael Howard
                            Archiver:
                            atibrewal@atlassian.com Aakrity Tibrewal

                              Created:
                              Updated:
                              Resolved:
                              Archived: