Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

BigPicture is a popular project management and project portfolio management app for Jira. You can leverage its power with additional JQL keywords and functions that JQL Search Extensions provides.

On this page:

Table of Contents

Integration points

Scope definition

JQL Search Extensions helps to define a precise scope of BigPicture boxes.

...

  1. Create a filter in Extended Search.

  2. Wait for BigPicture to sync the filters list (see the note below).

  3. Use the filter in BigPicture’s box configuration: Task → Scope Definition → Automatic Rules

BigPicture caches the list of filters and refreshes it every few hours.

Admins can force the refresh by clearing the BigPicture cache:

  1. Go toApps > Manage your apps > BigPicture configuration.

  2. Click on Clear cache

...

  1. .

Quick filters

You can use JQL Search Extensions keywords and filters in your BigPicture quick filters.

...

You can use JQL Search Extensions keywords and filters in the quick search bar.

...

  1. In the box view, click on the search loupe icon 🔍.

  2. Make sure the search is in the JQL mode - click on the ABC on the left to change the mode to JQL.

  3. Enter your JQL query.

Tip

...

In JQL, You can refer to filters with filter="Your filter name".

External use

It’s a common requirement to access the contents of a box outside of BigPicture, for example, to create a report in a 3rd party app or tool.

...

  • dashboard gadgets

  • boards

  • Jira search - simply use this the syntax, filter="Your filter name"

  • 3rd party apps that accept filters and JQL

...

Use cases

Source a subset of epics with their full hierarchy

You don’t need to add a whole Jira project to the scope of a box. You can create a box with selected epics and their stories and subtasks.

...

The above query could be limited to one project or it can source the issues from multiple projects.

Source a subset of initiatives with their full hierarchy

This use case is similar to the previous use case with epics. You can create a box with selected initiatives and all their children.

Depending on how Initiatives are configured, you can use the following methods to source a subset of initiatives.

Parent Link (Advanced roadmaps)

If you use the Parent Link then go with the childrenOfIssuesInQueryRecursive function:

...

  1. Create an Extended Search filter:
    key in (INT-2, INT-5, INT-8) OR issue in linkedIssuesOfQuery("key in (INT-2, INT-5, INT-8)", "your initiative link name")
    and call it “My initiatives and epics”

  2. Create another filter that is nesting a filter created in step 1:
    filter="My initiatives and epics" OR issue in childrenOfIssuesInQueryRecursive("filter='My initiatives and epics'")
    This filter matches:

    1. the selected initiatives and the linked issues (epics)

    2. all levels of children of the linked epics

  3. Use the filter as your scope in the box configuration

Source issues linked to your project

You may want to create a box with issues from your project and external issues that are linked to your project.

...

  1. Create an Extended Search filter:
    issue in linkedIssuesOfQuery("project=MYPROJ", "is blocked by")
    and call it “Blockers”

  2. Create another filter that nests the first filter:
    project=MYPROJ OR filter="Blockers" OR issue in childrenOfIssuesInQueryRecursive("filter='Blockers'")

  3. Use the filter as your scope in the box configuration

Highlight the blocked tasks

Create a quick filter:

linkType="is blocked by"

You can now see what tasks are blocked by other tasks.

Highlight the tasks with a high number of dependencies

Create a quick filter with JQL:

...

You can see the tasks that have a specific number of links. In this example, all the tasks with more than 2 links are going to be highlighted.

Highlight finished epics that have outstanding tasks

Create a quick filter with JQL:

...