Optimize engineering flow metrics using Jira data

Go to your Jira instance and configure a Jira quick filter.

To monitor epics in Jira, you can use the following JQL query as an example.

type = Epic AND project = <your-project-name> AND (resolved is EMPTY or resolved > -2w)

Select Copy filter. The Copy filter dialog opens.

Enter the name of the filter in Name.

Select who can view in the Viewers drop-down list.

The filter needs to be visible to the actor of the automation. To be on the safe side, set the permission so that everybody can see the filter.

For more information on actors in Jira automation, see What is a rule actor?.

Select Save.

Get the filter ID from the Jira URL. The format is similar to /issues/?filter=<filter-id>, for example, ?filter=12345

Go to Jira and open your Jira project.

Select Project settings.

On the left side, select Automation.

Select Create rule. Start with an empty Jira automation rule, allowing you to configure the correct fields.

Select the Scheduled trigger. For more information, see Jira automation triggers and Jira Automation: Set 'Scheduled' as a trigger and use multiple actions.

In the Occurrence field, to trigger nightly, for example, at 4:00 AM.

Select the Run a JQL search and execute actions for each work item in the query checkbox.

Required In the JQL field, enter the filter you created earlier as filter=<filter-id>. Replace <filter-id> with the ID of the filter that you created earlier.

Select Next to finish the configuration of the scheduled trigger.

Add a Send web request action.

Enter your Web request URL from the Dynatrace: Copy Endpoints path step. The pattern is https://{your-environment-id}.live.dynatrace.com/platform/ingest/v1/events.sdlc.

In the HTTP method field, select POST.

In the Web request body, select Custom data.

In the Headers section, set the following Key and Value pairs:

Replace <your-API-token> with your Dynatrace API access token that you generated in the earlier step.

Enter the following URL https://<your-endpoint>.atlassian.net/rest/api/2/issue/<your-issue>?expand=names into your browser. Replace <your-endpoint> with your URL. Replace <your-issue> with any of your issue keys.

Open the URL. This request returns a JSON output to the browser.

Search for the custom fields Rank and Team. You can use the custom field ID in the Jira Automation to send the data to your dashboard.

The field format is customfield_xxxxx where xxxxx is the field ID. The code block below shows an example of the JSON response body, including custom field IDs.

{
   "expand": "renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations",
   "id": "10000",
   "self": "https://<your-endpoint>.atlassian.net/rest/api/2/issue/10000",
   "key": "SCRUM-1",
   "names": {
      "customfield_10001": "Team",
      "customfield_10019": "Rank"
   }
}

Go to your Jira Automation.

In the Custom data field, enter the following template for generating JSON from JIRA issue data:

{
   "specversion": "1.0"
   , "id": "{{issue.key}}"
   , "source": "JIRA"
   , "day": "{{now.jiraDate}}"
   , "version": "1"
   , "key": "{{issue.key}}"
   , "summary": {{issue.summary.asJsonString()}}
   , "type": "{{issue.issuetype.name}}"
{{#exists(issue.assignee)}}
   , "assignee": "{{issue.assignee.displayName}}"
{{/}}
{{#exists(issue.customfield_<your-team-custom-field-id>)}}
   , "team": "{{issue.customfield_<your-team-custom-field-id>.name}}"
{{/}}
   , "status": "{{issue.status.name}}"
   , "status_category": "{{issue.status.statuscategory.name}}"
{{#exists(issue.resolution)}}
   , "resolution": "{{issue.resolution.name}}"
{{/}}
{{#if(not(issue.labels.isEmpty))}}
   , "labels": [
      {{#issue.labels}}
         "{{.}}" {{^last}},{{/}}
      {{/}}
      ]
{{/}}
{{#if(equals(issue.fixVersions.size, 1))}}
   {{#issue.fixVersions}}
   , "fix_version": "{{name}}"
   , "fix_version.release_date": "{{releaseDate.format("yyyy-MM-dd")}}"
   {{/}}
{{/}}
   , "created": "{{issue.created}}"
   , "status_changed_on": "{{issue.statuscategorychangedate}}"
   , "resolved": "{{issue.resolved}}"
   , "rank": "{{issue.customfield_<your-rank-custom-field-id>}}"
   , "project": "{{issue.project.key}}"
}

This example uses Jira smart values to extract the required information and ingest it into Dynatrace.
{{#if(equals(issue.fixVersions.size, 1))}} implies that the Jira epic has only one fix version.

Replace <your-rank-custom-field-id> with the Rank custom field ID.

Replace <your-team-custom-field-id> with the Team custom field ID.

Select Next to finish the configuration of the Send web request action.

Select Turn on rule to save the automation.

Enter the Name for the Jira Automation.

Select Turn on rule to save.

Go to Settings > Process and contextualize > OpenPipeline > Software development lifecycle.

Go to the Pipelines tab.

Select Pipeline.

Enter a pipeline Name.

Go to the Storage tab.

Select Processor > Bucket assignment.

Enter a New Processor Name, for example, Jira Daily Snapshot.

Set the Matching condition to source == "JIRA".

In the Storage drop-down list, select your bucket from the previous step.

Select Save.

Go to the Dynamic routing tab.

Select Dynamic routing.

In the Add a new dynamic route dialog, enter the Name of the new dynamic route.

In the Matching condition, enter source == "JIRA".

Select from the Pipeline drop-down your custom pipeline.

Select Add.

Select Save.

Run the Jira automation manually to verify the automation rule.

Query the events via DQL, for example, in Notebooks, to verify that your events have been ingested successfully.

Go to the Engineering Flow Metrics dashboard on Playground.

Download the dashboard.

Upload the dashboard to your environment.

The sections Epic Throughput, Lead Time, and Implementation Aging Chart are populated immediately after the first data import.

After the daily snapshot data is available for at least two weeks, you can do the analysis with the help of different sections of the dashboard, for example, Epic Burndown, Cumulative Flow Diagram, Work In Progress, Backlog Stability, and Changes.

The dashboard shows: