Searching for issues using Advanced Roadmaps details

In Jira, you can use JQL to search for issues that use Advanced Roadmaps custom fields. You can also use JQL to search for issues, by using Advanced Roadmaps issue fields.

Searching for issues

1. Perform an advanced search for issues. See Advanced searching to learn how.
2. Go to the following sections below, depending on what you're trying to achieve with your search.

For searching issues within the hierarchy

• For issues using the "parent link" field

  • For child issues of a parent issue, type Parent Link = EX-000.
  • For child issues of multiple parent links, type Parent Link in (EX-000, EX-001,EX-002, EX-003).
  • Other JQL operators that you can use include: IS EMPTY and IS NOT EMPTY

• For child issues of an issue

  • For child issues of an issue from a specific hierarchy level in Advanced Roadmaps, type issuekey in childIssuesOf("EX-000").
  • For instance, you have this hierarchy:
    • INIT-001 (at initiative hierarchy level)
      • EPIC-001 (at epic hierarchy level)
      • EPIC-002
        
        • STORY-001 (at story hierarchy level)
        • STORY-002
    To get the child issues of INIT-001, type issuekey in childIssuesOf("INIT-001"). All child issues below INIT-001 will be returned, and not just the child issues at the epic hierarchy level. This means EPIC-001, EPIC-002, STORY-001, and STORY-002 will be returned. 
  • If needed, you can skip returning issues of the hierarchy levels you don't need. For instance, if you want to return just the story-level issues, type issuekey in childIssuesOf("INIT-001") AND issueType != Epic.

• For parent issues of an issue

  • For parent issues of an issue in a specific hierarchy level in Advanced Roadmaps, type issuekey in parentIssuesOf("EX-000").
  • For instance, you have this hierarchy:
    • INIT-001 (at initiative hierarchy level)
      • EPIC-001 (at epic hierarchy level)
      • EPIC-002
        
        • STORY-001 (at story hierarchy level)
        • STORY-002
  • To get the parent issues of STORY-001, type issuekey in parentIssuesOf("STORY-001"). All parent issues above STORY-001 will be returned, and not just the immediate parent issue at the epic hierarchy level. This means EPIC-002 and INIT-001 will be returned.
  • If needed, you can skip returning issues of the hierarchy levels you don't need. For instance, if you want to return just the initiative-level issues, type issuekey in parentIssuesOf("STORY-001") AND issueType != Epic.

For issues using the "team" field

Note that you can only search for shared teams via JQL.

• For issues assigned to a specific team, type Team = "shared team name".
• For issues assigned to any set of teams, type Team in ("Shared team 1", "Shared team 2", "Shared team 3").
• Other JQL operators that you can use include: NOT IN, IS EMPTY, and IS NOT EMPTY

For issues that have target dates

• For issues that have a specific target start date or target end date, type Target start or Target end = "date".
• Other JQL operators that you can use include: !=, >, <, <=, and >=

For issues in a specific plan

• To search for issues in a specific plan, type issuekey in issuesInPlan(54), where 54 is the unique ID of the plan.
• For example, you have this URL for your plan:
  https://teamsinspace.atlassian.com/secure/PortfolioPlanView.jspa?id=54&sid=68#backlog
The plan ID in the URL is 54.

For issues in a specific program

• To search for issues in a specific program, type issuekey in issuesInProgram(30), where 30 is the unique ID of the program.
• For example, you have this URL for your program:
  https://teamsinspace.atlassian.com/secure/PortfolioProgramView.jspa?id=30#schedule
The program ID in the URL is 30.