This page is your step-by-step document serves as your comprehensive guide to running initiating Delivery Flow for the first time. It shows how you can access outlines the process of accessing flow metrics for your work tasks in 4 simple four straightforward steps.
Step-by-step guide to accessing your flow metrics
...
Comprehensive Instructions for Accessing Your Flow Metrics
Setup Establish Issue ColorsDecide what JQL query to use Color Coding
Execute Query and get your the Query to Obtain Your Flow Metrics
1.
...
Generate a Workflow Map using a Project Template
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Only application administrators can create Workflow Maps. |
After installing the appapplication, navigate proceed to the following options in Jira's the top menu of Jira:
Apps> Manage Your Apps>
SubsequentlyNext, access navigate to the following section in the Left Side Bar:
Delivery Flow Admin> Workflow Maps
Upon completion of successfully completing these steps, you will be presented with a screen resembling similar to the one below will be displayed:
...
Click on the New Map button. The New Workflow Map dialog dialog for creating a new workflow map will appear:
...
Click on the Use existing project as a template selection box. The dropdown will list display the name of all projects in your Jira instance. All projects will appear with the project name and , each accompanied by its unique project key. Select Choose the project that you wish intend to focus on. A Workflow Map Name is will be automatically generated. Change if required and then click Create.The newly created Workflow Map will now appear Modify it if necessary, then proceed to click Create. Make a note of the project used as we will refer to this in step 3.
Subsequently, the newly generated Workflow Map will be visible on the Workflow Maps Admin Page. This map has used leverages the selected project to determine define lanes and values in within the workflow map. At this stagepoint, you have the ability to can edit the Workflow Map if should it does not meet align precisely with your exact requirements.
2.
...
Establish Issue
...
Color Coding
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Only application administrators can set Issue Colors. |
This step is optional but recommended. Many graphs in Delivery Flow show display data at an Issue Type level. By default, every each Issue Type is represented denoted by the color grey. Assigning colors to different issue types helps with identification of issue types and also introduces consistency across your organisation as these are system settings.Navigate to aids in identifying them and promotes consistency throughout your organization, as these settings are system-wide.
To access the Color Mapping Page from , follow these steps in Jira's top menu:
Apps> Manage Your Apps>
SubsequentlyThen, access navigate to the following section in the Left Side Bar:
Delivery Flow Admin> Color Mapping
From here you can map Within this section, you can define and assign colors to your various issue types. For detailed instructions, you can refer to the guide on mapping colors to your issue types.
3.
...
Determine the Appropriate JQL Query
...
With Color and Workflow Map setup complete, all that is left to do the final step to access your Flow Metrics is to enter input and execute run a JQL query that captures encompasses all the work you wish intend to measure. Your query however, requires a little thought. Typically you will need to consider the scope of the query. Do I want data for my team, a group of teams or the whole organisation. You also need to consider time. Some projects exist for a very long time. Just providing scope without providing a time limit may result in the retrieval of an excessive amount of irrelevant data. Here are some suggestionsHowever, your query demands careful consideration. Primarily, you must contemplate the query's scope. For example, are you seeking data for your team, a cluster of teams, or the entire organisation?
Additionally, you must factor in time. Certain projects have extensive durations. Merely specifying the scope without setting a time constraint could lead to the extraction of an overwhelming volume of irrelevant data. Here is a simple example to get started:
Focus on project used to create Workflow Map
| Tip |
|---|
Project in (TEAM) AND updated >= startOfWeek(-12) |
Hopefully, this is an obvious strategythe strategy is apparent. The Workflow Map we created developed in step 1 will be able to interpret analyze the Jira workflow that these issues have travelled passed through, creating accurate generating precise metrics for all of the issues in the query. We used The example above refers to project TEAM in our example. Replace Substitute this value with the key of the project that you selected. This Query also limits at the query to approximately 12 weeks worth of data.
Focus on project and specific issues
| Tip |
|---|
Project in (TEAM) AND issuetype in (Story, Bug, Risk, Debt) AND updated >= startOfWeek(-12) |
Ideally, we want to measure everything in the system but before we get to that, it may make sense to reduce the scope of your initial measurements. It's not unusual to initially focus of development activities only. Many projects contain issue types that represent work that exists outside development. The above query narrows the scope to the specific development issue types in this project. Amend the project and issue type values to what is most relevant in your environment.
| Info |
|---|
The options for your query are endless. In general, we are trying to ship products to our customers. Think about your product, all the teams involved and all the work they are doing. The query that accurately encapsulates this is what you should be aiming for. |
...
chose in step 1. Additionally, this query restricts the data retrieval to approximately 12 weeks.
| Info |
|---|
The possibilities for your query are vast. Overall, our objective is to deliver products to our customers. Consider your product, the various teams engaged, and the extensive work being carried out. Your goal should be to formulate a query that encapsulates this work. |
4. Execute the Query to Obtain Your Flow Metrics
Navigate to the Delivery Flow App Page from Jira's top menu:
Apps> Delivery Flow>
This action will bring direct you to the main page of the appapplication.
...
Click on User Settings located in the top right corner of app. The the application. This action will prompt the user settings dialog will to appear.
...
Click on the Preferred Workflow Map selection box and select choose the Workflow Map that was created in step one. If not already set, enter 90 for the number of days in flow calculations. Click Save to save your settings and return to the main screen. Now enter , input your JQL query in the Delivery Flows query bar located at the top of the page and hit press enter. Delivery Flow will retrieve your data, perform conduct its flow calculations, and populate the app application with you your flow metrics.
...
Once execution of the query is complete, you will have access to the Flow Overview, Flow Types, Flow Demand,Flow Times and Flow History pages.You are now in a position to refine your query and repeat its execution if necessary. You can also adjust your Workflow Map or create new Workflow Maps for other projects or products being developed within your organisation.