10X: Field Dictionary for Feature Creation

The table below presents the primary fields used to create a feature in Jira Align, along with their meanings, field types, and allowable values: 

* - field can be managed using Details Panels Settings

Data Field Required/Optional Description/Purpose Field Type Values/Validations
Title Required The feature's title. Text Free-form
Description Optional The feature's description. Text Free-form
State Required Indicates where in the development process the feature is. Rigid hierarchy is required, as this drives many reports and workflows in Jira Align.  Drop-down System-defined:
-Pending Approval
-Ready to Start
-In Progress
-Dev Complete
-Test Complete
-Accepted
Type Optional* Type of feature being developed. For example, a feature may be architecture-related, or it can deliver direct business value. Drop-down System-defined:
-Not set
-Business
-Enabler
-Non Functional
-Architectural
MMF Optional* Shows whether the feature is a part of the minimum marketable feature. This option is critical for optimal flow and impact. Drop-down Yes or No
Blocked Optional* Blocked status alerts stakeholders that the development of this feature is currently blocked. Drop-down Yes or No
Priority Optional* Rank the priority of the feature vs. other features. Drop-down System-defined:
-Low
-Medium
-High
-Critical
Primary Program Required Assigns the feature to a primary program. Drop-down All programs in the system that the user is a member of are available for selection.
Approach Required* Defines whether a feature is assigned to only a single program, or if the work for the feature will span across multiple features. Drop-down Single Program Feature
Multi-Program Feature
Theme Optional* Associates the feature with a higher-level work object that is intended to span many PIs if not years. Drop-down If enabled, themes are added at the enterprise level. To be included in the drop-down, the theme must be created and must already be associated with the selected primary program and PI.
Owner Optional* The person ultimately responsible for the end delivery of the feature. Drop-down Users in system
Parent Epic Optional Defines the epic to which the feature is contributing. Drop-down  System-defined list based on the selected primary program 
Program Increments Optional* Assigns a feature to the PIs that it is intended for development in. A feature always inherits the parent's PI. If a feature has a capability or an epic, then the feature can only be assigned to the program increments assigned to the parent. If no parent is assigned, then all PIs based on the selected program are shown. If a parent has no PIs selected, then the feature has Unassigned Backlog as an option. Drop-down All available program increments that are associated with the selected program are included. Unlike epics, features must belong to a single PI
Release Vehicle Optional* Associates the feature with a release vehicle (e.g., a market-facing release that represents code getting pushed to a production environment). Multi-select Any available release vehicle in the system that is associated with the selected PI
Target Sprint: Target Start Optional* The target date that the development team intends to begin work on the feature. Primarily used for waterfall-style projects. Not tied to the actual work objects and the sprints/PIs they are associated to. Date Must be before Target Completion Date
Target Sprint: Target Completion Optional* The target date that the development team intends to complete work on the project. Primarily used for waterfall-style projects. Not tied to the actual work objects and the sprints / PIs they are associated to. Date Must be after Target Start Date
Team Week Estimate / T-Shirt / WSJF/ Points Optional* User-defined estimate of the effort required to complete the feature. Varies Varies
Tags Optional* When desired categorization is not provided, allows the user to tag/label feature with any free form item for use in filtering reports. Text Any
Report Color Optional Color for reporting puposes. Palette Standard color palette with RGB settings
Product Required (if enabled) Associates a feature to a specific product / product family for roadmapping and reporting purposes. Drop-down All available products that have been added to system
Dates: Portfolio Ask Optional* This date is set early in the process by the portfolio groups when they do their planning to request the delivery date for a feature. Calendar Any date
Dates: Start/Initiation Optional* This date indicates when the feature will start. It is used to do the strategic planning activities more effectively.  Calendar This is not the actual start date of the feature based on when the first story is done. This is the target start date based on intentions of the person submitting the feature.
Dates: Target Completion Optional*  This date indicates what the target completion date is. It is used to do the strategic planning activities more effectively.  Calendar Reflects the date the scheduler believes the feature can actually be completed (versus the Portfolio Ask date which is the date the business wants the feature to be delivered).
Lock/Reset Optional When you click Lock next to the dates, the dates are saved. Links When locked, the following additional fields are saved: story estimate and feature estimate. You can view this data together with the history of changes by clicking the information icon. Click Unlock to set new dates.
Category Optional* Enables user to categorize feature by the genericized reason a feature is under development (e.g., R&D, Growth, Tech Debt). Drop-down Drop-down options are created by administrator. All defined values are available for selection.
Business Driver Optional* The underlying reason (e.g., market driver) for the feature being developed Drop-down Drop-down options are created by administrator. All defined values are available for selection.
Developmental Step Optional* Ties the story to a value stream process step; used to provide a continuous flow of value through the agile process.  Drop-down   Available value stream process steps tied to selected program
Affected Countries Optional* Associates the feature with a selected market/country that it is being developed for. Multi-select Standard country list
Business Unit  Optional  The associated business unit of the organizational structure, created at the enterprise level.  Drop-down Business Unit is added at the enterprise level 
Capitalized Optional* Used to indicate if the feature is eligible for capitalization. When selected, stories within the feature (and the underlying stories/tasks) become eligible for captilization and the data for those tasks/stories/features are rolled up as capitalized on relevant reports. Drop-down Yes or No
Source Optional* Associates the feature with the type of requirement that triggered the need for the feature. Drop-down User-defined values, created via Configuration page of Administration module
Customers Optional* Associates the feature with customers available in the system. Multi-select Drop-down options are created by administrator. All defined values are available for selection.
Requester *Optional Ties the feature to the person that requested it, such as a customer or product owner. Drop-down List of Jira Align users 
Associated Ticket Optional* Associates the feature with a Support ticket. Text Free-form
Benefits Optional* Describes the value of this feature, answering the question "what's in it for the customer?" Text Free-form
Was this article helpful?
1 out of 1 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.