Filter Jira Align Roadmap initiatives by program using saved JQL

The decision: show only one program’s initiatives on the roadmap

You need a Jira Align roadmap that displays initiatives for a single program, such as “Alpha,” without showing work from other programs. The useful takeaway is to use a saved Roadmap filter with basic JQL in Timeline view rather than building a custom script. Saved filters are supported UI functionality; custom hierarchy filters require unsupported automation and can break after upgrades.

Constraints and assumptions

• You are working in Jira Align, not Jira Software.
• The Roadmap page is available and you have permission to create and save filters.
• A custom field named “Program” exists on the Initiative issue type and is indexed.
• You want to filter by program, not by team, capacity, or release.

Supported options compared

Option	Setup	Hierarchy filtering	Official support	Timeline view	Bar chart view	Maintenance
Saved Roadmap filter with JQL	Low; built-in UI	No; issue fields only	Yes	Respected	Aggregates by time range; filter not reliable	Low
Custom scripted function / automation	High; requires admin	Yes; parent and program fields	No; unsupported	Possible	Possible	High; may break on upgrade

Trade-offs

A saved JQL filter is the safer default because it uses Jira Align’s native filter UI and does not require custom code. The limitation is that JQL operates on issue fields, so you cannot write a direct hierarchy condition such as “parent capability belongs to program Alpha.” You must rely on the “Program” field being populated on each Initiative.

A custom scripted function can traverse hierarchy, but it adds maintenance overhead and is not officially supported. Jira Align upgrades can change automation behavior, so a script that works today may stop filtering correctly after a release. Use this path only if the Program field cannot be populated reliably and you have capacity to maintain custom automation.

View mode also decides the approach. The Bar chart view aggregates duration by time range and does not reliably apply a saved filter to the visible initiative set. The Timeline view applies the saved filter, so it is the correct choice for precise program slicing.

Create and validate the saved filter

Run these steps in the Jira Align Roadmap UI. You need a user account with Roadmap access and permission to save filters. Replace placeholders with your values.

1. Open Roadmap from the main navigation.
2. Click Filter, then Saved Filters.
3. Create a new filter named Program <program-name> Initiatives, replacing <program-name> with the actual program value, such as Alpha.
4. Enter the following JQL, replacing <project-key> and <program-name> with your values:

project = <project-key> AND issuetype = Initiative AND "Program" = "<program-name>"

Expected check: the filter preview should list only initiatives assigned to that program. If the list is empty, confirm that initiatives have the Program field populated and that the field is indexed.

Risk: an unindexed custom field can make the query slow on large instances. Monitor query time and contact your Jira Align administrator if results take longer than expected.

Verify the result

1. Select the saved filter Program <program-name> Initiatives from the Roadmap filter dropdown.
2. Confirm that every visible initiative has the Program field set to <program-name>.
3. Switch to Timeline view and confirm the time span matches the filtered initiatives.
4. Switch to Bar chart view and observe whether the filter is applied. If initiatives outside the program still appear, treat this as expected Bar chart behavior and rely on Timeline view for the filtered set.
5. Open an initiative’s detail view and confirm its Program field value matches the filter.

Limitations

• Basic JQL cannot filter directly on hierarchy relationships such as Capability-to-Program links.
• Filter performance may degrade with large instance sizes.
• The Bar chart view aggregates by time range and cannot be reliably limited by a saved filter.
• The Program custom field must exist and be indexed; otherwise the filter will be slow or return no results.
• Custom scripted functions are unsupported and may break after Jira Align upgrades.

Reversing the change

Creating a saved filter is a configuration change, but it is non-destructive. If you no longer need the filter, open Roadmap > Filter > Saved Filters, select the filter, and delete it. No roadmap data is modified.

Review note: This draft describes established Jira Align behavior but requires verification against your current Jira Align version and instance configuration before publication. Confirm field names, view behavior, and saved-filter support in your environment.