Create charts using Linear cycles
Create charts using Linear cycles
With Screenful, you can get reports of the current cycle or any of your previous cycles in Linear. You can aggregate cycle data across multiple teams into one chart. Create custom charts, including burndown charts, cumulative flow, and more.
With Screenful, you can get reports of the current cycle or any of your previous cycles in Linear. You can aggregate cycle data across multiple teams into one chart. Create custom charts, including burndown charts, cumulative flow, and more.
With Screenful, you can get reports of the current cycle or any of your previous cycles in Linear. You can aggregate cycle data across multiple teams into one chart. Create custom charts, including burndown charts, cumulative flow, and more.
Track Linear cycle with a burndown chart
To create a burndown chart, navigate to the Charts tab and click 'Add new chart'. Search for "Burndown" to find the burndown template. Open the template and click Configure.
In the chart editor, you can pick Current cycle, Last completed cycle, or any of your past cycles from the Scope menu:
Complete the process by clicking Update chart. You'll see the burndown of the selected cycle:
The burndown chart shows the amount planned for the cycle and the amount completed so far. With the burndown chart, you can quickly see whether you are on time or behind in the cycle.
If you select Current cycle as the filter for the chart, it will always reflect the currently running cycle. If you have set work estimates to your tasks, you can change the unit to Estimates in the chart settings.
Track Linear cycle with a burndown chart
To create a burndown chart, navigate to the Charts tab and click 'Add new chart'. Search for "Burndown" to find the burndown template. Open the template and click Configure.
In the chart editor, you can pick Current cycle, Last completed cycle, or any of your past cycles from the Scope menu:
Complete the process by clicking Update chart. You'll see the burndown of the selected cycle:
The burndown chart shows the amount planned for the cycle and the amount completed so far. With the burndown chart, you can quickly see whether you are on time or behind in the cycle.
If you select Current cycle as the filter for the chart, it will always reflect the currently running cycle. If you have set work estimates to your tasks, you can change the unit to Estimates in the chart settings.
Group and filter by cycle
You can filter the charts by Cycle (assigned to). This will include all issues assigned to the selected cycle. Once the cycle ends, all or a subset of the issues are completed during the cycle. You can then use Cycle (Completed in) to see which tasks were completed during the cycle.
Once a cycle ends, all or a subset of the issues are completed during the cycle. You can filter the chart by Cycle (Completed in) to see which tasks were completed during the cycle.
You can group and filter charts with either Sprint (assigned to) or Sprint (Completed in), depending on whether you are interested in tracking assignments or completions during the sprint. In either case, you can pick Current sprint, Last completed sprint, or any of your past sprints to pinpoint the exact set of issues you want to include in the chart.
Group and filter by cycle
You can filter the charts by Cycle (assigned to). This will include all issues assigned to the selected cycle. Once the cycle ends, all or a subset of the issues are completed during the cycle. You can then use Cycle (Completed in) to see which tasks were completed during the cycle.
Once a cycle ends, all or a subset of the issues are completed during the cycle. You can filter the chart by Cycle (Completed in) to see which tasks were completed during the cycle.
You can group and filter charts with either Sprint (assigned to) or Sprint (Completed in), depending on whether you are interested in tracking assignments or completions during the sprint. In either case, you can pick Current sprint, Last completed sprint, or any of your past sprints to pinpoint the exact set of issues you want to include in the chart.
Cumulative flow of a cycle
The Cumulative Flow Diagram (CFD) shows the amount of work in different stages of your workflow during one or more cycles. This chart helps you to see trends and spot bottlenecks in your workflow.
Each coloured area of the chart represents the number of issues (or story points) in a specific workflow state on a given day during the cycle. The horizontal axis indicates time, and the vertical axis shows the number of tasks. You can identify bottlenecks by looking at the widening areas in the chart. Are tasks piling up in a specific workflow state or assignee?
Use the Cumulative flow chart for spotting bottlenecks during the cycle. An upward trend indicates progress towards the goal, and a flat trend indicates stalled progress.
Learn more about the Cumulative Flow chart for Linear
Cumulative flow of a cycle
The Cumulative Flow Diagram (CFD) shows the amount of work in different stages of your workflow during one or more cycles. This chart helps you to see trends and spot bottlenecks in your workflow.
Each coloured area of the chart represents the number of issues (or story points) in a specific workflow state on a given day during the cycle. The horizontal axis indicates time, and the vertical axis shows the number of tasks. You can identify bottlenecks by looking at the widening areas in the chart. Are tasks piling up in a specific workflow state or assignee?
Use the Cumulative flow chart for spotting bottlenecks during the cycle. An upward trend indicates progress towards the goal, and a flat trend indicates stalled progress.
Learn more about the Cumulative Flow chart for Linear
Track cycles across multiple Linear teams
With Screenful, you can get reports of the current cycle or any of your previous cycles. You can aggregate cycle data across multiple teams into one chart. Here's an example chart showing the number of story points completed by cycle:
You can get this chart by going to the Charts tab and searching Estimates by cycle from templates.
All charts can be filtered by any of your cycles. There are also special filters for the Current cycle, and the Last completed cycle, that help you to set the filter once and let it work for you for all your future cycles!
When your active cycle changes, the filter will automatically adjust to display the correct cycle.
Track cycles across multiple Linear teams
With Screenful, you can get reports of the current cycle or any of your previous cycles. You can aggregate cycle data across multiple teams into one chart. Here's an example chart showing the number of story points completed by cycle:
You can get this chart by going to the Charts tab and searching Estimates by cycle from templates.
All charts can be filtered by any of your cycles. There are also special filters for the Current cycle, and the Last completed cycle, that help you to set the filter once and let it work for you for all your future cycles!
When your active cycle changes, the filter will automatically adjust to display the correct cycle.
Create a cycle report from a template
You can create a cycle report for Linear using a report template. Go to the Reports tab and click Add new report:
A modal opens, showing the available templates. Select Current cycle as the template (use a keyword search if needed). A report containing key metrics from the current running cycle is created:
The Current cycle report for Linear shows the status of the current cycle - what is completed or in progress, the cycle burndown, cumulative flow, and more. You can also compare the velocity across multiple cycles and how much was allocated vs completed per cycle.
Create a cycle report from a template
You can create a cycle report for Linear using a report template. Go to the Reports tab and click Add new report:
A modal opens, showing the available templates. Select Current cycle as the template (use a keyword search if needed). A report containing key metrics from the current running cycle is created:
The Current cycle report for Linear shows the status of the current cycle - what is completed or in progress, the cycle burndown, cumulative flow, and more. You can also compare the velocity across multiple cycles and how much was allocated vs completed per cycle.
About Screenful
Screenful provides multidimensional analytics of the data in Linear. You can slice & dice your data with 15 different chart types, and click through to drill into details.
Analytics & Reports by Screenful is available in Linear integrations. For more information, see the guide for setting up Screenful with Linear.
About Screenful
Screenful provides multidimensional analytics of the data in Linear. You can slice & dice your data with 15 different chart types, and click through to drill into details.
Analytics & Reports by Screenful is available in Linear integrations. For more information, see the guide for setting up Screenful with Linear.
Book a free onboarding call
Need help with setting up your charts and reports? Don't find a metric you are looking for? Book a call with our expert. We'd love to help you supercharge your Jira reporting!
Book a free onboarding call
Need help with setting up your charts and reports? Don't find a metric you are looking for? Book a call with our expert. We'd love to help you supercharge your Jira reporting!
Learn more
Learn more
FAQ
Common questions
A data source is a Linear Team. The pricing is based on the number of teams you explicitly import to Screenful, not the total number of teams in Linear. One data source can contain any number of projects. You can compare plans on the pricing page.
You can import data sources from all the tools we support in the same Screenful account. Learn more about managing data sources.
A data source is a Linear Team. The pricing is based on the number of teams you explicitly import to Screenful, not the total number of teams in Linear. One data source can contain any number of projects. You can compare plans on the pricing page.
You can import data sources from all the tools we support in the same Screenful account. Learn more about managing data sources.
You can manage the subscription in the billing settings. The location of the billing settings depends on the product you are subscribed to. You can learn more by following the instructions in this guide.
You can manage the subscription in the billing settings. The location of the billing settings depends on the product you are subscribed to. You can learn more by following the instructions in this guide.
We do not make changes to your data. We only read it via the API of your tool. Screenful is only for reporting and analytics. It does not update any data within your tools.
We do not make changes to your data. We only read it via the API of your tool. Screenful is only for reporting and analytics. It does not update any data within your tools.
What is the difference between these metrics?
Reaction time = time before the work was started
Cycle time = time from start to completion
Lead time = Reaction time + Cycle time
Timing metrics explained: Lead time vs Cycle time
How is the reaction time calculated?
Reaction time starts running when a task is moved into a state that is mapped to the "Not started" in the workflow mapping. The reaction time stops when the task is moved out from that state. If the task is never placed into a state that is mapped to the “Not started” workflow state, then the reaction time is zero.
What if tasks skip lists/columns, or there is no sequential workflow?
The timing information is based on how long items stay in the workflow states that are mapped to "In progress" in the workflow mapping. There is no need for sequential progress, and it is totally fine if tasks skip some of the workflow steps.
What if a task is moved from the “not started” state directly to “done” without going through any of the “in progress” states?
In that case, the cycle time will be zero.
How does the cycle time work if a task is moved into "in progress" and then back to "not started yet"? Similarly, what happens if a card is archived while it's in progress?
Cycle time is calculated only for completed tasks, so in both of those cases, cycle time would be undefined.
If a task is moved from "in progress" to "done", but then back to "in progress" again for additional work would this time be added to the cycle time?
Cycle time is counted only when the task is in progress, so the time spent in the "done" state is not included in the calculation.
When is a task created? Does the clock start when a task is created or when it is put in the "next" state (or equivalent)?
The clock starts when a task is moved to a workflow state that is mapped to the "not started" or "in progress" workflow state.
Are weekends included in the cycle time calculations?
Weekends are included in the calculations by default, but you can change that in the chart settings by selecting 'Exclude non-business hours. See How to set weekend days and office hours
What is the difference between these metrics?
Reaction time = time before the work was started
Cycle time = time from start to completion
Lead time = Reaction time + Cycle time
Timing metrics explained: Lead time vs Cycle time
How is the reaction time calculated?
Reaction time starts running when a task is moved into a state that is mapped to the "Not started" in the workflow mapping. The reaction time stops when the task is moved out from that state. If the task is never placed into a state that is mapped to the “Not started” workflow state, then the reaction time is zero.
What if tasks skip lists/columns, or there is no sequential workflow?
The timing information is based on how long items stay in the workflow states that are mapped to "In progress" in the workflow mapping. There is no need for sequential progress, and it is totally fine if tasks skip some of the workflow steps.
What if a task is moved from the “not started” state directly to “done” without going through any of the “in progress” states?
In that case, the cycle time will be zero.
How does the cycle time work if a task is moved into "in progress" and then back to "not started yet"? Similarly, what happens if a card is archived while it's in progress?
Cycle time is calculated only for completed tasks, so in both of those cases, cycle time would be undefined.
If a task is moved from "in progress" to "done", but then back to "in progress" again for additional work would this time be added to the cycle time?
Cycle time is counted only when the task is in progress, so the time spent in the "done" state is not included in the calculation.
When is a task created? Does the clock start when a task is created or when it is put in the "next" state (or equivalent)?
The clock starts when a task is moved to a workflow state that is mapped to the "not started" or "in progress" workflow state.
Are weekends included in the cycle time calculations?
Weekends are included in the calculations by default, but you can change that in the chart settings by selecting 'Exclude non-business hours. See How to set weekend days and office hours
By default yes, but you can specify your working hours and days in the Account Settings.
By default yes, but you can specify your working hours and days in the Account Settings.
Yes, there are a few different ways you can filter out outliers from the charts, including
Filtering by item name
Filtering by how long an item has been in progress
Setting a label and filtering out based on that label
You can learn more from this guide: How to remove outliers from data?
Yes, there are a few different ways you can filter out outliers from the charts, including
Filtering by item name
Filtering by how long an item has been in progress
Setting a label and filtering out based on that label
You can learn more from this guide: How to remove outliers from data?
Does this support my specific workflow or do I have to use some specific states like "open", "in progress" and "done"?
You are not limited to any specific set of states or a workflow. You can configure your own workflow, if such exists, and you can use that in your reporting. It's also ok if you don't have any workflow in your boards, as can create reports based on any other criteria by setting a filter.
You are not limited to any specific set of states or a workflow. You can configure your own workflow, if such exists, and you can use that in your reporting. It's also ok if you don't have any workflow in your boards, as can create reports based on any other criteria by setting a filter.
All data sources are synced automatically once per hour. Changing settings or configuration will trigger additional sync so your data is at most one hour old. You can sync data manually at any time in the sync settings.
All data sources are synced automatically once per hour. Changing settings or configuration will trigger additional sync so your data is at most one hour old. You can sync data manually at any time in the sync settings.
You can embed any custom chart or report to any web page using the embed code. Learn more about the sharing feature from the online guide.
You can embed any custom chart or report to any web page using the embed code. Learn more about the sharing feature from the online guide.
The Getting Started Guide contains Instructions for setting up Screenful.
See also our Accounts & Pricing FAQ.
Check out our how-to and video tutorials, or get in touch by emailing support@screenful.com
The Getting Started Guide contains Instructions for setting up Screenful.
See also our Accounts & Pricing FAQ.
Check out our how-to and video tutorials, or get in touch by emailing support@screenful.com
FAQ
Common questions
A data source is a Linear Team. The pricing is based on the number of teams you explicitly import to Screenful, not the total number of teams in Linear. One data source can contain any number of projects. You can compare plans on the pricing page.
You can import data sources from all the tools we support in the same Screenful account. Learn more about managing data sources.
A data source is a Linear Team. The pricing is based on the number of teams you explicitly import to Screenful, not the total number of teams in Linear. One data source can contain any number of projects. You can compare plans on the pricing page.
You can import data sources from all the tools we support in the same Screenful account. Learn more about managing data sources.
You can manage the subscription in the billing settings. The location of the billing settings depends on the product you are subscribed to. You can learn more by following the instructions in this guide.
You can manage the subscription in the billing settings. The location of the billing settings depends on the product you are subscribed to. You can learn more by following the instructions in this guide.
We do not make changes to your data. We only read it via the API of your tool. Screenful is only for reporting and analytics. It does not update any data within your tools.
We do not make changes to your data. We only read it via the API of your tool. Screenful is only for reporting and analytics. It does not update any data within your tools.
What is the difference between these metrics?
Reaction time = time before the work was started
Cycle time = time from start to completion
Lead time = Reaction time + Cycle time
Timing metrics explained: Lead time vs Cycle time
How is the reaction time calculated?
Reaction time starts running when a task is moved into a state that is mapped to the "Not started" in the workflow mapping. The reaction time stops when the task is moved out from that state. If the task is never placed into a state that is mapped to the “Not started” workflow state, then the reaction time is zero.
What if tasks skip lists/columns, or there is no sequential workflow?
The timing information is based on how long items stay in the workflow states that are mapped to "In progress" in the workflow mapping. There is no need for sequential progress, and it is totally fine if tasks skip some of the workflow steps.
What if a task is moved from the “not started” state directly to “done” without going through any of the “in progress” states?
In that case, the cycle time will be zero.
How does the cycle time work if a task is moved into "in progress" and then back to "not started yet"? Similarly, what happens if a card is archived while it's in progress?
Cycle time is calculated only for completed tasks, so in both of those cases, cycle time would be undefined.
If a task is moved from "in progress" to "done", but then back to "in progress" again for additional work would this time be added to the cycle time?
Cycle time is counted only when the task is in progress, so the time spent in the "done" state is not included in the calculation.
When is a task created? Does the clock start when a task is created or when it is put in the "next" state (or equivalent)?
The clock starts when a task is moved to a workflow state that is mapped to the "not started" or "in progress" workflow state.
Are weekends included in the cycle time calculations?
Weekends are included in the calculations by default, but you can change that in the chart settings by selecting 'Exclude non-business hours. See How to set weekend days and office hours
What is the difference between these metrics?
Reaction time = time before the work was started
Cycle time = time from start to completion
Lead time = Reaction time + Cycle time
Timing metrics explained: Lead time vs Cycle time
How is the reaction time calculated?
Reaction time starts running when a task is moved into a state that is mapped to the "Not started" in the workflow mapping. The reaction time stops when the task is moved out from that state. If the task is never placed into a state that is mapped to the “Not started” workflow state, then the reaction time is zero.
What if tasks skip lists/columns, or there is no sequential workflow?
The timing information is based on how long items stay in the workflow states that are mapped to "In progress" in the workflow mapping. There is no need for sequential progress, and it is totally fine if tasks skip some of the workflow steps.
What if a task is moved from the “not started” state directly to “done” without going through any of the “in progress” states?
In that case, the cycle time will be zero.
How does the cycle time work if a task is moved into "in progress" and then back to "not started yet"? Similarly, what happens if a card is archived while it's in progress?
Cycle time is calculated only for completed tasks, so in both of those cases, cycle time would be undefined.
If a task is moved from "in progress" to "done", but then back to "in progress" again for additional work would this time be added to the cycle time?
Cycle time is counted only when the task is in progress, so the time spent in the "done" state is not included in the calculation.
When is a task created? Does the clock start when a task is created or when it is put in the "next" state (or equivalent)?
The clock starts when a task is moved to a workflow state that is mapped to the "not started" or "in progress" workflow state.
Are weekends included in the cycle time calculations?
Weekends are included in the calculations by default, but you can change that in the chart settings by selecting 'Exclude non-business hours. See How to set weekend days and office hours
By default yes, but you can specify your working hours and days in the Account Settings.
By default yes, but you can specify your working hours and days in the Account Settings.
Yes, there are a few different ways you can filter out outliers from the charts, including
Filtering by item name
Filtering by how long an item has been in progress
Setting a label and filtering out based on that label
You can learn more from this guide: How to remove outliers from data?
Yes, there are a few different ways you can filter out outliers from the charts, including
Filtering by item name
Filtering by how long an item has been in progress
Setting a label and filtering out based on that label
You can learn more from this guide: How to remove outliers from data?
Does this support my specific workflow or do I have to use some specific states like "open", "in progress" and "done"?
You are not limited to any specific set of states or a workflow. You can configure your own workflow, if such exists, and you can use that in your reporting. It's also ok if you don't have any workflow in your boards, as can create reports based on any other criteria by setting a filter.
You are not limited to any specific set of states or a workflow. You can configure your own workflow, if such exists, and you can use that in your reporting. It's also ok if you don't have any workflow in your boards, as can create reports based on any other criteria by setting a filter.
All data sources are synced automatically once per hour. Changing settings or configuration will trigger additional sync so your data is at most one hour old. You can sync data manually at any time in the sync settings.
All data sources are synced automatically once per hour. Changing settings or configuration will trigger additional sync so your data is at most one hour old. You can sync data manually at any time in the sync settings.
You can embed any custom chart or report to any web page using the embed code. Learn more about the sharing feature from the online guide.
You can embed any custom chart or report to any web page using the embed code. Learn more about the sharing feature from the online guide.
The Getting Started Guide contains Instructions for setting up Screenful.
See also our Accounts & Pricing FAQ.
Check out our how-to and video tutorials, or get in touch by emailing support@screenful.com
The Getting Started Guide contains Instructions for setting up Screenful.
See also our Accounts & Pricing FAQ.
Check out our how-to and video tutorials, or get in touch by emailing support@screenful.com
Troubleshooting
While both the public and private channels are shown in the menu, you won’t receive the report to a private channel without explicitly adding the Screenful app to that channel. Learn how to enable sending to a private Slack channel.
There can also be restrictions on who can install apps to your Slack. Learn how to manage app approval in your Slack workspace.
Some browser plugins may interfere with the authorization process. If you see an empty page during the authorization or the list of channels is empty, you should try with another browser (or ask your colleague to do the Slack authorization).
While both the public and private channels are shown in the menu, you won’t receive the report to a private channel without explicitly adding the Screenful app to that channel. Learn how to enable sending to a private Slack channel.
There can also be restrictions on who can install apps to your Slack. Learn how to manage app approval in your Slack workspace.
Some browser plugins may interfere with the authorization process. If you see an empty page during the authorization or the list of channels is empty, you should try with another browser (or ask your colleague to do the Slack authorization).
Filter options are derived from task data, which means that if you recently added some properties, such as labels, but haven't yet assigned them to any tasks, they won't show up in the filter options. As soon as you assign them to tasks, they will show up in the filter options from then on.
Filter options are derived from task data, which means that if you recently added some properties, such as labels, but haven't yet assigned them to any tasks, they won't show up in the filter options. As soon as you assign them to tasks, they will show up in the filter options from then on.
If you or your colleague didn't receive the user invitation email, you can go to the user settings and click the Copy invitation link button to copy the link to the clipboard. After that, you can share the link via any channel (email, Slack, Teams, etc). You can learn more from the user invitation guide.
If you or your colleague didn't receive the user invitation email, you can go to the user settings and click the Copy invitation link button to copy the link to the clipboard. After that, you can share the link via any channel (email, Slack, Teams, etc). You can learn more from the user invitation guide.
Troubleshooting
While both the public and private channels are shown in the menu, you won’t receive the report to a private channel without explicitly adding the Screenful app to that channel. Learn how to enable sending to a private Slack channel.
There can also be restrictions on who can install apps to your Slack. Learn how to manage app approval in your Slack workspace.
Some browser plugins may interfere with the authorization process. If you see an empty page during the authorization or the list of channels is empty, you should try with another browser (or ask your colleague to do the Slack authorization).
While both the public and private channels are shown in the menu, you won’t receive the report to a private channel without explicitly adding the Screenful app to that channel. Learn how to enable sending to a private Slack channel.
There can also be restrictions on who can install apps to your Slack. Learn how to manage app approval in your Slack workspace.
Some browser plugins may interfere with the authorization process. If you see an empty page during the authorization or the list of channels is empty, you should try with another browser (or ask your colleague to do the Slack authorization).
Filter options are derived from task data, which means that if you recently added some properties, such as labels, but haven't yet assigned them to any tasks, they won't show up in the filter options. As soon as you assign them to tasks, they will show up in the filter options from then on.
Filter options are derived from task data, which means that if you recently added some properties, such as labels, but haven't yet assigned them to any tasks, they won't show up in the filter options. As soon as you assign them to tasks, they will show up in the filter options from then on.
If you or your colleague didn't receive the user invitation email, you can go to the user settings and click the Copy invitation link button to copy the link to the clipboard. After that, you can share the link via any channel (email, Slack, Teams, etc). You can learn more from the user invitation guide.
If you or your colleague didn't receive the user invitation email, you can go to the user settings and click the Copy invitation link button to copy the link to the clipboard. After that, you can share the link via any channel (email, Slack, Teams, etc). You can learn more from the user invitation guide.