DevOps Integrations | Targetprocess - Visual management software
DevOps integrations for CI/CD, analytics and reporting
khakholka icon
Vitaly Khakholka
Targetprocess Product Specialist
Reproduction of Cezanne's Houses at L'Estaque - 1880 — Algorithm by Pindar Van Arman

Teams across many industries struggle to optimize product delivery and quality or increase transparency and predictability.

The new DevOps integrations in Targetprocess serve these goals and more. They compliment planning work in Targetprocess by adding visibility into the work in progress, workflow automation and comprehensive analytics at any point of the value delivery process.

Any integration in Targetprocess unlocks a number of possibilities immediately after it's been set up.

There are:

  • Simplified navigation between different systems
  • Data consolidation from multiple sources into Targetprocess
  • Automation across different tools
  • Analytics of processes running in different tools

Let's talk about these possibilities one by one.

Simplified navigation between different systems. 
 
watching time: 25 sec

If a company is using several tools or services, context switching is always an issue. It's a pain to switch from one tool to another and to know which item in one tool is connected to what data in another tool. We try to solve this in our integrations.

asset1

Consolidating data from 3rd-party tools in Targetprocess 
 
watching time: 1 min 8 sec

We add important information from third-party tools into Targetprocess. Therefore, Targetprocess becomes a source of information where you can quickly and easily see important things in one place.

asset2

Here is an example with a GitLab integration.

If you open a card in Targetprocess, you can see a specific work item. We quickly show all pull requests and branches related to this work and give you the ability to easily navigate to third-party systems (like GitLab, in this case).

asset3

We also show additional information, for example, the state of the merge request. Here you can see it's closed. You can see pipelines and the code review status for the specific branch.

asset4

All this information is available on the boards as an extra control.

asset5

Automation across different tools 
 
watching time: 1 min 7 sec

A very important component of Targetprocess is the sub-system of Automation Rules that we released not so long ago.

asset6

This is a very powerful development that lets you automate the processes inside your company. Originally, it was designed for some events happening in Targetprocess, so you could make changes to the data in Targetprocess. As a result we can trigger some actions and implement various business logic.

For example, if the state of the User story is changed, let's close the state of the new feature.

Today, with all the new integrations, we can also integrate third-party systems into our sub-system of automation rules.
asset7

This unlocks the possibility to create various new scenarios. For example, if the state of a card is changed and we move a User story to "tested", then please merge a pull request that is linked to this card.

Opposite-direction scenarios are also possible. For example, if a pull request has been merged, then let's change the state of the card in Targetprocess.

asset8
Our system of automation rules can also be used outside the Targetprocess context. If a company has Targetprocess, they can automate processes that happen outside of Targetprocess.

For example, in GitLab, if a pipeline passed for some service and the tests have been passed, we can trigger a pipeline with integration tests in another repository.

asset9
We can also automate scenarios between different 3rd-party tools

For example, if in GitLab a pull request has been merged and pipelines passed, let's trigger another pipeline in Jenkins.

asset10

As you can see, we gain the ability to automate processes that go beyond Targetprocess in a company and involve a certain set of tools the company uses, as long as we have integrations for these tools

Analytics of processes running in different tools 
 
watching time: 56 sec

This is the last important aspect. We perform all our integrations so they also integrate into our visualization system, our BI tool Vizydrop. This lets us build analytics using cross tool data. For example, we can build a report in Targetprocess that also incorporates GitLab's pull request data.

asset11

Here is a sample report built with the help of our DevOps integration: PR lead time by Teams.

asset12

If you go to Settings, you will see a new Data source called DevOps.

asset13

This report shows you the cycle time and the number of pull requests every team in Targetprocess has done over the last 90 days.

We take data from GitLab, map it to data in Targetprocess, and can see how different teams work. This can serve as a source of extra useful information because you can now analyze the efficiency of processes happening in other tools outside Targetprocess.

Here is another interesting report to look at: PRs Lead Time by Iteration.

asset14

How did the cycle time of pull requests of one team change over time?

This is our team, and we can see that in every sprint we worked differently. Our efficiency and approach to work have been changing. We see the cycle time of pull requests has been declining, so we made smaller changes in code, which is also indicative of the quality of processes inside the team.

Another example is the Areas of Responsibility report.

asset15

Here we can see which people are contributing to specific features in the system. A bubble shows the number of pull requests for a certain feature, and we can easily see how many pull requests have been made and reviewed, who made them, and for which features they have been made.

Time to sum it up.

What is our goal for DevOps integrations in Targetprocess?

We are working on the DevOps integrations with the following goals in mind:

finger-right icon
Simplify navigation
between systems.
food-stack icon
Source extra data into Targetprocess, consolidate 3rd-party data in Targetprocess so it becomes the single source of information, making work more convenient.
robot icon
Make it possible to automate the processes beyond Targetprocess and cover a large set of third-party tools.
mistery-ball icon
Provide analytics on all these processes that happen in third-party tools.
Quick jump to:
  • Simplified navigation between different systems
  • Consolidating data from 3rd-party tools in Targetprocess
  • Automation across different tools
  • Analytics of processes running in different tools

Who will benefit from these integrations?

The integrations influence multiple roles within the enterprise. The visibility, work status tracking, automation and reporting possibilities unlocked by the new integrations will benefit developers, as long as development team leads, QA, scrum masters, release engineers, IT leaders, business & finance.

What tools are currently available with DevOps integrations?

Here's an overview of the most popular tools:
Azure DevOps
Azure DevOps
Automatically associate branches and pull requests with Targetprocess entities
GitLab
GitLab
Automatically link branches and merge requests to Targetprocess entities.
GitHub
GitHub
Automatically associate branches and pull requests with Targetprocess entities.
Phabricator
Phabricator
Link code revisions with any Targetprocess entity.
Bitbucket
Bitbucket
Automatically associate branches and pull requests with Targetprocess entities.
Jenkins
Jenkins
Connect Targetprocess entities with work items, reflect issues back as Bugs or User Stories.
REQUEST INTEGRATION

Or start your
free trial

Enter your email
By clicking "Continue", you acknowledge and agree that we will process your personal data in accordance with our Service Privacy Policy and Terms of Service.

We’ve sent you a confirmation e-mail — please, go check it.

Get a live
product demo

Let one of our product specialists shape Targetprocess for your company needs.