Choosing Between Jira Align PI Objectives and Custom Fields for Strategic Work

Problem: How to track strategic work in Jira Align

When a portfolio uses Jira Align to run SAFe PI planning, the team often asks whether to capture strategic intent with the built‑in PI Objective object or to add custom fields on Initiatives or Epics. The choice affects visibility, roll‑up, and maintenance.

Decision Guide

Decision: Pick the method that balances SAFe alignment, reporting needs, and admin effort. Use native PI Objectives if the organization follows SAFe closely and needs program‑increment visibility. Use custom fields when the data is static, cross‑increment, or requires attributes not supported by PI Objectives.

Constraints to Evaluate

• SAFe Visibility – Must appear in PI Planning boards and Program Boards.
• Roll‑up Accuracy – Data should roll up automatically to Portfolio level.
• Integration with Jira Software – Changes must sync bidirectionally.
• Administrative Overhead – Consider field creation, permission, and future migrations.

Option Comparison

Feature	Native PI Objectives	Custom Fields on Initiatives/Epics
Framework Alignment	Built‑in SAFe object, fully supported by PI Planning	Generic, requires manual mapping to SAFe artifacts
Planning Workflow	Visible and editable directly on the PI Planning board	Not visible on the board, must be reviewed on issue screens
Roll‑up Logic	Automatic business‑value aggregation across Features and Stories	Requires custom aggregate rules or manual calculations
Admin Effort	Low – pre‑configured, no field mapping required	High – create field, add to screens, set permissions, map to Jira
Flexibility	Limited to business value, acceptance criteria, and description	Any data type (text, number, date, multi‑select) can be stored

Trade‑offs

• Native PI Objectives give you a ready‑made SAFe experience but can’t store domain‑specific metadata beyond the standard fields.
• Custom Fields let you capture any attribute but you lose the automatic roll‑up and board visibility, and you must maintain the mapping and permissions.

Implementation: Using Native PI Objectives

1. Log in as a Jira Align administrator.
2. Navigate to Administration → PI Objectives and confirm the feature is enabled.
3. Create a sample PI Objective: Create → PI Objective, fill in Business Value and Acceptance Criteria, and link it to a Feature.
4. Open the PI Planning board for the relevant Increment and verify the objective appears in the Objectives column.
5. Check that the objective’s Business Value rolls up to the Portfolio view under Strategic Themes.

Implementation: Adding Custom Fields for Strategic Tracking

1. Navigate to Administration → Custom Fields and click Create.
2. Choose Text (or another type) and name the field Strategic Pillar. Set the scope to Initiative and Epic.
3. Add the field to the relevant screens: Initiative Detail and Epic Detail.
4. Configure permissions so that the Program and Portfolio roles can view and edit the field.
5. In Jira Software, create a new custom field (matching the name) and add it to the Initiative/Epic issue type screen. Map the field to the Jira Align custom field via the Field Mapping section.
6. Create an Initiative, set the Strategic Pillar value, and link it to a Jira issue. Verify the value appears in both Jira Align and Jira Software.
7. To enable roll‑up, add a Portfolio Aggregation Rule that sums the field value across all Epics linked to the Initiative, or use a custom report.

Verification Checklist

• Native PI Objectives: Visible on PI Planning board, Business Value appears in Portfolio roll‑up, no sync errors.
• Custom Fields: Value displays on Initiative/Epic screens, syncs to Jira, aggregation rule produces correct totals in Portfolio view.

Limitations and Migration Notes

Switching from custom fields to native PI Objectives (or vice versa) requires data migration. Existing reports that rely on the custom field will need to be rewritten, and any automated aggregation rules must be updated. Plan migrations during a release cycle to avoid disrupting PI planning.

Conclusion

If strict SAFe alignment and program‑increment visibility are priorities, native PI Objectives are the safer, lower‑maintenance choice. For organizations that need to track additional strategic metadata that persists across multiple PIs, custom fields provide the necessary flexibility but add administrative overhead and require careful configuration of sync and aggregation rules.