See what's new on Keypup! Ā šŸ“¢

Activity Pipe

Template providing all unclosed items (including Pull Requests and Issues) classified by development stage.

Get started with this Dashboard

Get a Dynamic Agile Board View from Your Gits and PM Tools

with

Activity Pipe

Monitor your software development lifecycle progress with the dynamic agile board combining cards from your git(s) and project management tool(s).

Use the Activity Pipe Board
Activity PipeActivity PipeActivity Pipe

Understand the Activity Pipe Board

Instead of traditional agile boards like Jira or Trello, the activity pipe board uses dynamic filters and updates itself automatically as issues and pull requests progress. Pre-configured activity pipe boards follow a common developer-oriented flow. Implementing issues requires a pull request. An issue disappears from the "Todo" column as soon as a pull request relates to it, and the pull request appears in the "In development" section. When a pull request gets a reviewer assigned, it will move from the ā€œin developmentā€ column to the in review column.

Prior to merging, pull requests must have green builds and enough approvals to move from the in review column to the ā€œmergeableā€ column. Items are marked as complete based on their implementation status: Recently closed issues and pull requests will appear in the ā€œdoneā€ column. In addition, any open issue with related pull requests merged will appear in the ā€œdoneā€ column (ā€œResolution state = Implemented ā€).

How to Use the Activity Pipe Board

The purpose of this board is not to replace your standard agile board (e.g., Jira, Trello). Instead of using it for tracking issues, it should be used as a tool for tracking pull requests based on their contextual status.

You can fully customize the activity pipe board. For example, columns can be added and removed (up to 10) and filters can be edited. If you want to list all open pull requests that haven't been updated in the last three days, you can add a column called ā€œin developmentā€ (stuck) next to ā€œin developmentā€. You may then edit the ā€œin developmentā€ column to exclude pull requests that have not been updated in the last three days. This approach will allow you to immediately see which pull requests need your attention.

Looking to Monitor Your Own Activity Pipe?

As a software engineer, you may want to track this metric at an individual level to keep track of your own activities.Ā This version of the template comes with a filter automatically applied to allow you to monitor your own Activity Pipe.

Use the Activity Pipe Board

Understand the Activity Pipe Board

Instead of traditional agile boards like Jira or Trello, the activity pipe board uses dynamic filters and updates itself automatically as issues and pull requests progress. Pre-configured activity pipe boards follow a common developer-oriented flow. Implementing issues requires a pull request. An issue disappears from the "Todo" column as soon as a pull request relates to it, and the pull request appears in the "In development" section. When a pull request gets a reviewer assigned, it will move from the ā€œin developmentā€ column to the in review column.

Prior to merging, pull requests must have green builds and enough approvals to move from the in review column to the ā€œmergeableā€ column. Items are marked as complete based on their implementation status: Recently closed issues and pull requests will appear in the ā€œdoneā€ column. In addition, any open issue with related pull requests merged will appear in the ā€œdoneā€ column (ā€œResolution state = Implemented ā€).

How to Use the Activity Pipe Board

The purpose of this board is not to replace your standard agile board (e.g., Jira, Trello). Instead of using it for tracking issues, it should be used as a tool for tracking pull requests based on their contextual status.

You can fully customize the activity pipe board. For example, columns can be added and removed (up to 10) and filters can be edited. If you want to list all open pull requests that haven't been updated in the last three days, you can add a column called ā€œin developmentā€ (stuck) next to ā€œin developmentā€. You may then edit the ā€œin developmentā€ column to exclude pull requests that have not been updated in the last three days. This approach will allow you to immediately see which pull requests need your attention.

Looking to Monitor Your Own Activity Pipe?

As a software engineer, you may want to track this metric at an individual level to keep track of your own activities.Ā This version of the template comes with a filter automatically applied to allow you to monitor your own Activity Pipe.

Use the Activity Pipe Board