Start loading
Initiation of the loading procedure is done by selecting the button with the "+" icon in the main menu of Wiveez (on the left).
You then access a page containing the list of Agile projects and boards on your Jira Cloud server. By default, the "Project" part is selected.
The user can select the period over which he wishes to measure the indicators.
1 month : Loading all tickets in the project that have been in "Done" status in the last 30 days, relative to the upload date + all tickets in "To do" status or " In progress ";
3 months: Loaded all project issues that have been in "Done" status in the last 90 days, relative to the upload date + all tickets in "To Do" status or " In progress ";
6 months: Loaded all project issues that have been in "Done" status in the last 180 days, relative to the upload date + all tickets in "To Do" status or " In progress ";
1 year: Loading all tickets in the project that have been in "Done" status in the last 365 days, relative to the upload date + all tickets in "To do" status or " In progress ";
All: Loading of all project tickets;
Custom: Definition of the ticket loading period, by entering a start date and an end date. Loading of all tickets in the project that have been in "Complete" state, over the selected period + all tickets in "To do" or "In progress" state;
Start: Definition of the start date for loading tickets, by entering a start date. Loading all tickets in the project that have been in "Complete" status, between the entered start date and the project upload date + all tickets in "To Do" or "In Progress" status.
The initiation of the import is done via the "Import" button.
The user has the option to cancel the upload via the "Cancel" button.
Product loading
Launching the loading of a project is done in the background, so as not to block the user during data recovery.
The user can, at any time, follow the progress of the loading and the estimated time remaining.
As soon as the loading is complete, the total number of tickets loaded and displayed and the user can start the configuration phase of the Wiveez product. via the "BEGIN CONFIGURATION" button.
Configure a product
Step 1 of 3 - Configure ticket types
Jira allows you to create an infinite number of ticket types, named “issue types”.
In order for Wiveez to be able to offer you metrics and indicators (KPIs) reflecting your product, you must differentiate the types of tickets to be used in the calculation.
You must also allow the application to differentiate the types used for anomalies (bugs). This allows the application to tell you the anomaly rate, by Product, Version (FixVersion), Feature (Jira Epic) and Label.
For these two settings, you need to check the corresponding boxes in the list of ticket types:
It is useless and not recommended to check the type dedicated to Features (“Epic”) for the calculation of the indicators presented in the dashboards dedicated to each Feature. Features detection and calculation is done automatically.
Select the "Apply" button to proceed to the next step.
Step 2 of 3 - Configure Workflow
Jira allows you to create a workflow adapted to each project or type of issue.
Jira also logs all the steps created on a workflow, whether they are used or not.
When loading a product in Wiveez, all the states (steps) of the workflow are transmitted.
You must then choose which states (steps) Wiveez must use to calculate the indicators.
To do this, you must define which states will be represented in the three main categories of the flow: To Do, In Progress (WIP, Work In Progress) and Done.
Moving from a workflow state to the Wiveez workflow is done by dragging and dropping (drag & drop) from the top column (Jira workflow) to the bottom one (Wiveez workflow).
Situation before selecting workflow states (example):
Situation after assigning Jira workflow states in Wiveez workflow (example):
A status defined as "To Do" in Jira can be used in a "To Do", "In Progress" or "Done" column of the Wiveez Workflow. The same goes for Jira's other "In Progress" and "Done" states. It is not imperative to use the same category for a step.
It is not mandatory to use all Jira states in the Wiveez workflow.
The order of the states, recalled using the number to the left of the name, is important and defines the way ticket transitions will be interpreted to reconstruct the workflow traversal in Wiveez.
Select the "Apply" button to go to the next step.
Step 3 of 3 - Configure Wiveez Workflow States for Efficiency Calculation
In order to be able to calculate the efficiency indicator of the Wiveez workflow, you must indicate which are the states on which an activity is carried out and which are waiting states.
By default, "To do" states are pending states. On the contrary, all "In Progress" states are considered to have activity and are therefore activated in the list.
Example of efficiency configuration:
Select the "Apply" button to go to the next step.
Calculation of metrics and indicators
Once the product configuration is finalized by clicking on the "Close" button, the calculation of metrics and indicators starts automatically.
The calculation is based on tickets meeting the configuration criteria:
having a ticket type of those selected;
being in one of the states of the Wiveez workflow (one of the 3 bottom columns).
The efficiency calculation is done on the same tickets, the active and inactive time based on the configuration you entered for the states.
This calculation is done in the background. You can, if you wish, leave Wiveez to use Jira or open another product in Wiveez using the portfolio.
As soon as the calculation of the indicators is finished, you have direct access to the product, via the summary dashboard.
For more information, you can consult the documentation of ce tableau de bord as well as les autres proposés by Wiveez.