About this report
The feature audit report shows which features are associated with a PI as well as the feature status. The report is beneficial to product owners and release train engineers for assessing and tracking feature progress during a PI. This report is generated by selecting a specific PI and optionally a program.
To navigate to this report:
If you’re using the new navigation:
- Select Programs in the top navigation bar and select the program you want to view information about.
- On the sidebar, select Reports in the list of options.
- Select Feature audit report; the report displays.
If you’re using the old navigation:
- Select the Reports icon from the left Navigation menu.
- Start typing the report's name in the Search box.
- Once found, select the report.
Note: You can also use the categories on the left to search for the needed reports.
- PI must exist in the system and be tied to a program.
- Features must be created and assigned to PIs.
- Features must be assigned to capabilities or epics.
How are report values calculated?
- Feature ID: ID of the feature in the selected PI; auto-assigned at feature creation.
- Feature Name: Name of the feature in the selected PI; created on the features page/New Feature panel.
- PI: PI the feature is associated with; selected on the features page/New Feature panel.
- Epic or Capability: Epic or capability the feature is associated with; assigned via the epics/capabilities page or New Epic/Capability panel.
- Created Date: Date when the feature was created; value is pulled from the features page.
- In Progress: Date when the feature went to the In Progress state; value is pulled from the features page.
- Dev Complete: Date when the feature went to the Dev Complete state; value is pulled from the
- features page.
- Test Complete: Date when the feature went to the Test Complete state; value is pulled from the features page.
- Accepted: Date when the story went to the Accepted state; value is pulled from the features page.
How to interpret this report
As the PI progresses, features should move through the approval process and advance through the In Progress, Dev Complete, and Test Complete states. Ultimately, at the end of the PI, features should be in the Accepted state. Use this report to achieve the goal of creating a development cadence, which will provide predictability and confidence in future work.