JIRA-based Coding Time

JIRA-based Coding Time

By default, LinearB will calculate Coding Time as the time between when the first commit has been made on a branch to when a PR is submitted. This feature enables customers to track coding time by Jira issue status. Coding Time would be tracked from when a Jira issue linked to a git branch is moved from "To Do" to "In Progress" to when a pull request is opened.

This setting would be implemented at the org level (impacting all teams).

How to enable Jira-based Coding Time:

To enable this feature, go to Company Settings, and click on the Advanced tab. At the bottom of this settings page, select "By Jira Issue state combined with PR" from the Coding Time Strategy section. Click Save.


  • For LinearB to match Git work to Jira issues, all Git branches must be matched to Jira issues.
  • For more information on matching branches with Jira issues, please see Naming conventions - Jira

Known behavior:

  • If a branch is not matched to a Jira issue, LinearB will fall back to counting the time of the first code commit as the beginning of Coding Time.
  • When multiple Jira tickets are connected to the same branch, LinearB will count the oldest ticket as the coding start-time.
  • LinearB locks branches from updates after they are merged. If a Jira ticket is created and linked to a branch after the branch has been merged, LinearB will ignore the matched ticket and the Coding Time will be calculated using the time of first commit.
  • If a Jira ticket is marked as “in progress” after a PR is issued for a branch, LinearB will fall back to using the first commit as the beginning of coding time.


  • For best results, we recommend opening a Jira ticket for every branch created.
  • Use LinearB's unmatched branches alerts to help identify unmatched branches.

How did we do?

Powered by HelpDocs (opens in a new tab)