Table of Contents
Managing Project Trackers in Jira
Create, edit, and delete project tackers.
This article applies to Jira-connected workspaces.

Overview
Project trackers in LinearB allow you to group and measure delivery metrics based on your team’s actual scope of work. Rather than relying solely on board-level data, you can define a custom set of filters—like specific epics, labels, or fields—to track progress, predict risk, and improve delivery outcomes for cross-functional or initiative-based projects.
Each tracker provides clear visibility into how work is progressing, aligned with your team’s real priorities.
Creating a Jira Project Tracker
- In the LinearB side menu, click Projects > Delivery.
- On the Projects page, click Create Project. The Create new project form opens.
- Enter a unique Project Name. (The name cannot match an existing team.)
- Select the Jira Boards to include in the project. You must select at least one Jira board in order to create a tracker.
- Under Methodology, choose either Scrum or Kanban.
- In the Project Scope section, click + Add filter to define your team’s scope of work. You can filter issues based on the following criteria:
- Epic - Useful when your team’s work is centered around specific initiatives.
- Label - Ideal for filtering work items by team or work type across large boards.
- Field - Any custom field used to tag or group issues in your Jira instance.
- Fix version, Component, etc.
- Define Iteration Controls (optional):
- Use regular expressions to include or exclude specific iterations.
- This helps limit work to only the sprints or timeframes relevant to your team.
- Click Save.


Building Queries Using LinearB's Project Rules
LinearB's Project Rules allow you to create powerful, customized queries by combining multiple filters, such as boards, epics, labels, or fields. By understanding how these filters interact, you can fine-tune your rules to collect precisely the issues you need.
How Filters Work Together in Jira
- Adding multiple filters of the same type (e.g., boards, labels):
Filters of the same type are combined using an OR operator. For example, if you add two boards, the rule will collect all issues from either board. - Combining different filter types:
Filters of different types are combined using an AND operator. For instance, if you add a label to your rule, LinearB will collect issues from the specified boards that also contain the added label.
Rule-Writing in Boolean Terms
To better visualize how rules work, think of them as Boolean logic:
- Adding multiple items within a single filter type (e.g., several boards) creates an OR relationship:
(Board A OR Board B)
- Adding another filter type (e.g., a label) creates an AND relationship with the previous filters:
(Board A OR Board B) AND Label X
This approach ensures you can refine your results to match your project’s specific needs, collecting only the issues that meet all the defined criteria.
Description | I want to view issues from either the "LINB board" or the "CS board" that are labeled as either "UI-issue" or "Backfill". This query should combine the selected boards using an OR condition, and within those boards, filter issues that match any of the specified labels. |
Boolean | |
LinearB Interface | ![]() |

Suggestions for Projects
Collecting Issues from Multiple Boards or Specific Epics
You can collect issues from multiple boards or just from specific epics, as described below:
- In the Create new project form, name your new project name.
- Click + Select Jira Boards. Select the Jira Boards to include in the project, and click Add.
- Select the methodology (Scrum or Kanban).
- Click + Add Filter.
- Select the filter type you want to use, such as Epics or Labels.
- If required, click Add to confirm your selections.
- Click Save.
LinearB will retrieve all issues from the selected boards or epics. To refine your results further, you can add additional filters, such as Fields or Fix Versions, ensuring your project includes only the most relevant issues.
Filtering Specific Labels or Fields Within a Board or Epic
To focus your project on issues from specific boards or epics that also meet additional criteria (e.g., have a certain label or field), follow these steps:
- Add filters for the required boards or epics by following the steps above.
- Repeat the process to add the Labels or Fields you want to use for filtering.
This ensures that only issues matching both the board/epic and the label/field criteria are included in your project.
Collecting Issues Based on Labels or Fields Globally
LinearB also allows you to collect issues using specific labels or fields across all boards, without the need to define a board or epic. This is ideal for tracking types of work across your entire team. For example:
- Issues labeled "technical debt"
- Issues tagged as "infrastructure work"
This global filtering capability enables you to monitor cross-team efforts effortlessly and maintain a unified view of work priorities.


Editing a Jira Project Tracker
Once a project is created, its issue collection rules are displayed under the associated board name. As your project evolves, you can modify these rules to adapt to changing requirements by adding or removing filters as needed.
- Click the ellipse ⋮ located next to your Project Delivery Tracker, and select Edit Project.
- Make the required changes:
- Add or remove rules to refine how issues are collected.
- Switch the project's workflow between Scrum and Kanban as needed.
- Save your updates. The project updates take effect within 15 minutes.

By keeping your project rules up to date, you can ensure that the data collected remains aligned with your team’s current goals and workflow.

Deleting a Project Tracker
Click the ellipse ⋮ located next to the Project Delivery Tracker you want to delete, and select Delete Project.

How did we do?
Marking Projects as Favorites