Extension Definition
Streamline software and IT projects by predicting completion, reducing costs, and increasing velocity.
| Analyses and Business Questions | |
| Metrics | |
| Dimensions | |
| Concepts | |
| Internal Comparisons | This application does not include additional Internal Comparisons |
| What If and Planning Models | This application does not include additional What If and Planning Models |
| Subjects | |
| Events | This application does not include additional Events |
| Overlays | This application does not include additional Overlays |
Core Blueprint V1.30.31
June 24, 2025
An analysis is a document that describes a collection of analytical content to analyze and understand a particular use case. While you can generate your own Analysis, each Visier application is delivered with a set of standard analyses.
| Display Name | Description | Business Questions | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| How can we track team productivity and issues progress? | Review team productivity and issues progress towards nearest release. | |||||||||||||||||||
| Issue - Validation | Validate the issues that developers are working on. |
| ||||||||||||||||||
| Learn About Issue Metrics | Learn about the different types of issue metrics available in the Jira Extension. |
|
A metric is a value that is computed from the Subject and Events for a particular group of entities in a particular time frame. An example of a metric is "Turnover Rate."
| Display Name | Description |
|---|---|
| Average Direct Cost of Issues Closed in Period (Issue Process) | The average direct cost of Jira issues that were closed during the period and have a Done status at the end of the period. |
| Average Velocity (Issue Process) | The average number of story points for Jira issues that moved from In Progress to Done status during the specified timeframe. |
| Average Velocity (Issue Process) (Trailing 12 M) | The average number of story points for Jira issues that moved from In Progress to Done status during the specified timeframe. |
| Direct Cost of Epics | The direct cost of Jira epics at the end of the period. |
| Direct Cost of Story Points for Child Issues (Issue Process) | The direct cost of story points for child issues of Jira epics that closed during the period and have a Done status at the end of the period. |
| Issue Cycle Time (Issue Process) | The average amount of time, in days, for a Jira issue to move from In Progress to Done status. |
| Issue Cycle Time (Issue Process) (Trailing 12 M) | The average amount of time, in days, for a Jira issue to move from In Progress to Done status. |
| Issue Lead Time (Issue Process) | The average amount of time, in days, for a Jira issue to move from To Do to Done status. |
| Issue Lead Time (Issue Process) (Trailing 12 M) | The average amount of time, in days, for a Jira issue to move from To Do to Done status. |
| Issues Closed in Period (Issue Process) | The total number of Jira issues that closed during the period and have a Done status at the end of the period. |
| Issues Open in Period (Issue Process) | The total number of Jira issues that had an In Progress or To Do status during the period. |
| Stagnant Epics (Issue Process) | The total number of open Jira epics whose latest updated child issue is older than the specified age threshold at the end of the period. |
| Story Point Velocity per Sprint (Issue Process) | The total amount of cycle time, normalized by sprint length days, for a Jira issue to be completed. |
| Story Points Completed in Period (Issue Process) | The total number of story points for Jira issues that closed during the period and have a Done status at the end of the period. |
| Story Points Completed per Developer (Issue Process) | The average number of story points for Jira issues completed per developer at the end of the period. |
| Story Points Open in Period (Issue Process) | The total number of story points for Jira issues that had an In Progress or To Do status during the period. |
| Story Points for Exited Employees (Issue Process) | The total number of story points for Jira issues that have a To Do or In Progress status, that were assigned to employees who exited the organization during the period. |
| Time to Release | The average amount of time, in days, until the release date of the fix version that the Jira issue belongs to. |
| Total Direct Cost of Issues Closed in Period (Issue Process) | The total direct cost of Jira issues that closed during the period and have a Done status at the end of the period. |
| Total Story Points for Child Issues (Issue Process) | The total number of story points for child issues of Jira epics at the end of the period. |
| Total Story Points for Epics | The total number of story points for Jira epics at the end of the period. |
A dimension is created from a concept or property and contains all the potential values. It is then used to allow filtering and grouping of the content. Dimensions can be hierarchical. An example of a dimension is "Generation" which groups employees by the year of their birth.
| Display Name | Description |
|---|---|
| Component | The name of the component that the Jira issue belongs to. |
| Fix Version Name | The name of the fix version assigned to the Jira issue. |
| Issue Priority | The priority level assigned to the Jira issue (e.g., Now or Nice to Have). |
| Issue Status | The status of the Jira issue (e.g., To Do, In Progress, or Done). |
| Issue Type | The type of Jira issue (e.g., Bug or Epic). |
| Project Name | The name of the project that the Jira issue has been created under. |
| Resolution | The resolution that has been assigned to a Jira issue with a Done status (e.g., Won't Fix or Fixed). |
Visier employs a large range of analytical concepts, these define expected and desired analytical objects. Each concept allows configuration so that the concept can be employed by you. An example of a concept is "Involuntary Turnover" which allows you to define the types of turnover that are to be considered as involuntary.
| Display Name | Description |
|---|---|
| Bug | Whether or not a Jira issue is a bug. |
| Developer | Whether or not the employee's occupation is within software development. |
| Epic | Whether or not a Jira issue is an epic. |
| Feature Work | Whether or not a Jira issue is a child issue of an epic. |
| Story | Whether or not a Jira issue is a story. |
| Target Version | The fix version of the next release that is being targeted. |
| Task | Whether or not a Jira issue is a task. |
Subjects are entities that evolve and change. They have properties and changes to those properties are captured over time. An example of a subject is "Employee."
| Display Name | Description |
|---|---|
| Employee | Current employees of the organization. |
| Issue | A task related to software development. |
| Issue Assignee | The intermediate subject containing information about employee assigned Jira issues. |