Investment Profile

LinearB's Investment Profile allows you to see how development efforts are allocated across different customizable investment categories.


KTLO (Keeping the Lights On)

The minimum tasks a company is required to perform in order to stay operational on a daily level while maintaining a stable level of service. This might include activities such as:

  • Maintaining current security posture
  • Service and ticket monitoring & troubleshooting
  • Maintaining current levels of service uptime

Developer Experience

This is defined as the actions performed to improve the productivity of development teams and their overall experience of work. This might include activities such as:

  • Better developer tooling
  • Testing automation
  • Code restructuring
  • Work to reduce the size of the KTLO bucket in the future

Feature Enhancements

This is defined as actions taken to enhance features or deliver a product that ensures customer satisfaction.This might include activities such as:

  • Customer requested improvements
  • Improved performance/utilization
  • Iterations to improve adoption/retention/quality
  • Improved product reliability or security

New Value

This is defined as the actions performed to invest in new features that increase revenue and growth by new customer acquisition or expansion. This might include activities such as:

  • Adding a new feature
  • Supporting a new platform or partner application
  • Implementing roadmap work

Inefficiency Pool

Based on research conducted by the LinearB Data Science Team, we’ve found that engineering teams can increase their capacity by addressing inefficiencies in their development lifecycle.

The inefficiency pool in LinearB estimates the portion of your resource pool that you could reclaim with these efficiency improvements (like implementing developer automation tools).

This estimate is based on the current effort wasted as a result of pull request idle time, the number of full-time employees in your org, and the total days worked in the given period.

The Inefficiency Pool can be enabled and disabled by checking the checkbox under Investment Benachmarks and click Save.

How to Configure Your Investment Profile Report

To configure which types of Jira issues are collected click on the Configure icon in the top right of your Investment Profile page, and select the investment category you want to edit.

  • Click Edit Rule to add additional filters
  • Click Add Rule to add an additional rule to your Investment Profile bucket
    • Note each Investment Profile bucket can have up to 3 rules.

Adding 2 and 3 boards or labels to a rule will collect all issues that match any of these items. Each additional filter added to a rule will refine and filter the issues collected.

Thinking of rule-writing in Boolean terms; adding multiple boards will combine the boards using an OR operator. If you then add a filter for a label, LinearB will pull any issue that is included in the boards AND also must contain the label.


I want to see issues of type "Bug" which are of priority "Highest", or "Blocker", or "Critical", or "High", or "Major"


(Type:"Bug") AND (Priority:"Highest" OR "Blocker" OR "Critical" OR "High" OR "Major")

LinearB Interface

Filtering Options:
  • Issue Types: The types of Jira Issues to be collected in this bucket, for example, "Bug" or "Task" issue types.
    • Note that each Jira issue type must be explicitly selected. For example: selecting "Bug" will not also pull in issues of the "Critical Bug" type.
  • Labels: Filter by Jira Labels applied to tickets.
    • Note that this field requires an exact match (case sensitive, etc.)
  • Custom Fields: Currently LinearB supports both string and number custom fields.
    • Note that this must be an exact match.
  • Keywords: Searches for the use of text in both the issue type and issue summary.
    • This query is not case sensitive.
    • Searching by issue type using keywords does not require an exact text match, and would gather all issue types that contain the keyword you are searching for.

How did we do?

Powered by HelpDocs (opens in a new tab)