Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Adding the Parent Feature Name and Program Increment (PI) Fields to Jira Software

Jira Align has the ability to push Program Increment (PI) and the Parent Feature name data to a custom field in Jira Software from Jira Align Features to Jira Epics.

Whether this custom field is already in place or one is being created for the first time, please be aware of the following best practices: 

Jira Configurations

This is a one-way push from Jira Align to Jira Software — only Jira Align can push Program Increment and Parent Feature data as these fields are not native to Jira Software. Jira Align is the system of record for these fields upon integration.  

Within Jira, Navigate to Settings > Issues > Custom Fields > Click "Add Custom Field".  In the top right of the application Select Advanced Field Types > Select "Text Field (read only) > Create a custom field for Parent Feature Name and repeat for Program Increment.

Add these fields to the create, edit, and view screens within your integrated Jira Projects.

Jira Align Configurations

To connect Parent Feature Name and Program Increment data to your Jira Software custom fields, log into Jira Align and navigate to Administration > Connectors > Jira Settings > Jira Setup > Custom Fields. Next, scroll down to the Parent Feature Name and Program Increment fields and enter your custom field IDs in the following format: customfield_100xx, where "100xx" is the ID located in Jira Software.



Note - after adding these fields you will need to update the work items in Jira Align to force the sync on legacy work items.   


1 comment

I've used this before successfully with a 3-tier hierarchy:

  • Portfolio Epics
    • Program Features
      • Team Stories

In that context, there was no confusion as Features were the children of Epics, and the parent Epic field worked as expected.

Now I just started with another client who uses solutions and capabilities.  The hierarchy becomes:

  • Portfolio Epics
    • Solution Capabilities
      • Program Features
        • Team Stories

Can someone confirm what the integration will replicate to the custom field configured as the "parent epic" in this configuration?  Will it populate the parent capability?  Or the grand-parent Epic?

(sorry, just started on this account and don't have a test environment available yet to just try it; anyway, it probably does not hurt for this article to document the behavior precisely)


Log in or Sign up to comment
Community showcase
Published in Jira Align

Lean Portfolio Management with Jira Align

Lean Portfolio Management (LPM) is a relatively newer management methodology which draws from lean and systems thinking approaches to drive value-based outcomes, as opposed to more traditional techni...

1,350 views 2 30
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you