Linear units, metrics, and properties
Linear units, metrics, and properties
This page describes the available units, metrics, and issue properties when creating a chart for a Linear data source.
See also these related resources
Chart editor guide
Group and filter by label groups
Screenful Knowledge base
Units
Units are the numbers shown in the charts. Unit can be any of these:
Issue | The default unit is Issue i.e. a chart displays the count of issues and sub-issues. |
|---|---|
Estimates | Linear's default estimation field to describe the size of an issue. |
Time in state | Timing metrics (reaction, lead, cycle time). These are calculated for all issues and sub-issues. |
All units share these characteristics:
They can be filtered by any property of an issue
They can be summarized as sum, average, or median
They can be formatted as numbers, monetary units, or time units
Metrics
Metrics are the calculations performed on the selected unit.
Total | Shows the total amount of the selected unit in the selected data sources. |
|---|---|
Not started | Work not started according to the workflow settings. |
Not started & In progress | Incomplete work according to the workflow settings. |
In progress | Work in progress according to the workflow settings. |
Created (within date range) | Issues by creation date (issue creation date from the Linear API). |
Completed (within date range) | Issues by Date completed. The last date & time when the issue was completed (moved to a state mapped as done in the workflow settings). |
By Due date | Issues by Due date. Includes the items that have a Due date within the selected date range (regardless of their workflow state). |
Reaction time (avg, completed items) | Time before the work was started. The average time spent in the states mapped as Not started in the workflow settings. |
Reaction time (sum, completed items) | Time before the work was started. The sum of time spent in the states mapped as Not started in the workflow settings. |
Cycle time (avg, completed items) | Time from start to completion. The average time spent in the states mapped as In progress in the workflow settings. |
Cycle time (sum, completed items) | Time from start to completion The sum of time spent in the states mapped as In progress in the workflow settings. |
Lead time (avg, completed items) | Lead time (avg) = (Reaction time + Cycle time) (avg) |
Lead time (sum, completed items) | Lead time (sum) = (Reaction time + Cycle time) (sum) |
Time in state (avg, completed items) | Time spent in specific workflow states. Use the filter to select the states. |
Time in state (sum, completed items) | Time spent in specific workflow states. Use the filter to select the states. |
Issue properties
Issue properties that can be displayed as columns in a Task list.
Archived at | The time when the issue was archived. |
|---|---|
Assignee | The assigned person |
Assignees | The assigned persons (if multiple) |
Canceled at | The time when the issue was canceled. |
Completed on time | Was the item completed before the due date (true/false). |
Component | The Component the issue is currently assigned to. |
Created by | The person who created the issue. |
Cycle (assigned to) | The cycles the issue has been assigned to. |
Cycle (completed in) | The cycle the issue was completed in. |
Cycle time | Time from start to completion. The time spent in the states mapped as In progress in the workflow settings. |
Cycle time (working hours) | Time from start to completion. The time spent in the states mapped as In progress in the workflow settings. Time is calculated only within the set working days and hours. |
Data source | The Linear team the item is currently in. |
Date completed | The last date & time when the issue was completed (moved to a state mapped as done in the workflow settings). |
Date created | Item creation date (from the Linear API). |
Date updated | Last update date (from the Linear API) |
Due date | Issue Due date. |
Estimate | Linear's estimate field to describe the size of an issue. |
Issue ID | Unique identifier of the issue (from the Linear API). |
Issue name | Name of the issue. |
Item type | Issue or sub-issue. |
Label | The labels added to the issue. |
Lead time | Reaction time + Cycle time |
Lead time (working hours) | Reaction time + Cycle time. Time is calculated only within the set working days and hours. |
Mapped state | Mapped workflow state according to the workflow settings. Either Not started, In progress, or Done. |
Milestone | The project milestone the issue is assigned to. |
Moved to mapped state | Time when the item was moved to its current mapped workflow state. |
Moved to workflow state | Time when the item was moved to its current workflow state. |
Parent | Parent item of the issue (if any). |
Priority | The Priority of the issue. |
Project | The Project the issue is currently in. |
Reaction time | Time before the work was started. The time spent in the states mapped as Not started in the workflow settings. |
Reaction time (working hours) | Time before the work was started. The time spent in the states mapped as Not started in the workflow settings. Time is calculated only within the set working days and hours. |
Reopened | Whether the issue has been reopened (true/false) |
Started at | The time when the issue was started (from the Linear API) |
Started triage at | The time when the triage was started (from the Linear API) |
State | The issue workflow state |
State (open/done) | Whether the issue's mapped state is Open (Not started or In progress) or Done. |
Team | The team the issue is assigned to. |
Time in progress | The time spent in the states mapped as In progress in the workflow settings. |
Time in progress (working hours) | The time spent in the states mapped as In progress in the workflow settings. Time is calculated only within the set working days and hours. |
Time in workflow state | The time spent in the current workflow state. |
Timings | The total time spent in each workflow state. |
Triaged at | The time when the triage was completed (from the Linear API) |
Workflow state | The current workflow state of the issue. |
This page describes the available units, metrics, and issue properties when creating a chart for a Linear data source.
See also these related resources
Chart editor guide
Group and filter by label groups
Screenful Knowledge base
Units
Units are the numbers shown in the charts. Unit can be any of these:
Issue | The default unit is Issue i.e. a chart displays the count of issues and sub-issues. |
|---|---|
Estimates | Linear's default estimation field to describe the size of an issue. |
Time in state | Timing metrics (reaction, lead, cycle time). These are calculated for all issues and sub-issues. |
All units share these characteristics:
They can be filtered by any property of an issue
They can be summarized as sum, average, or median
They can be formatted as numbers, monetary units, or time units
Metrics
Metrics are the calculations performed on the selected unit.
Total | Shows the total amount of the selected unit in the selected data sources. |
|---|---|
Not started | Work not started according to the workflow settings. |
Not started & In progress | Incomplete work according to the workflow settings. |
In progress | Work in progress according to the workflow settings. |
Created (within date range) | Issues by creation date (issue creation date from the Linear API). |
Completed (within date range) | Issues by Date completed. The last date & time when the issue was completed (moved to a state mapped as done in the workflow settings). |
By Due date | Issues by Due date. Includes the items that have a Due date within the selected date range (regardless of their workflow state). |
Reaction time (avg, completed items) | Time before the work was started. The average time spent in the states mapped as Not started in the workflow settings. |
Reaction time (sum, completed items) | Time before the work was started. The sum of time spent in the states mapped as Not started in the workflow settings. |
Cycle time (avg, completed items) | Time from start to completion. The average time spent in the states mapped as In progress in the workflow settings. |
Cycle time (sum, completed items) | Time from start to completion The sum of time spent in the states mapped as In progress in the workflow settings. |
Lead time (avg, completed items) | Lead time (avg) = (Reaction time + Cycle time) (avg) |
Lead time (sum, completed items) | Lead time (sum) = (Reaction time + Cycle time) (sum) |
Time in state (avg, completed items) | Time spent in specific workflow states. Use the filter to select the states. |
Time in state (sum, completed items) | Time spent in specific workflow states. Use the filter to select the states. |
Issue properties
Issue properties that can be displayed as columns in a Task list.
Archived at | The time when the issue was archived. |
|---|---|
Assignee | The assigned person |
Assignees | The assigned persons (if multiple) |
Canceled at | The time when the issue was canceled. |
Completed on time | Was the item completed before the due date (true/false). |
Component | The Component the issue is currently assigned to. |
Created by | The person who created the issue. |
Cycle (assigned to) | The cycles the issue has been assigned to. |
Cycle (completed in) | The cycle the issue was completed in. |
Cycle time | Time from start to completion. The time spent in the states mapped as In progress in the workflow settings. |
Cycle time (working hours) | Time from start to completion. The time spent in the states mapped as In progress in the workflow settings. Time is calculated only within the set working days and hours. |
Data source | The Linear team the item is currently in. |
Date completed | The last date & time when the issue was completed (moved to a state mapped as done in the workflow settings). |
Date created | Item creation date (from the Linear API). |
Date updated | Last update date (from the Linear API) |
Due date | Issue Due date. |
Estimate | Linear's estimate field to describe the size of an issue. |
Issue ID | Unique identifier of the issue (from the Linear API). |
Issue name | Name of the issue. |
Item type | Issue or sub-issue. |
Label | The labels added to the issue. |
Lead time | Reaction time + Cycle time |
Lead time (working hours) | Reaction time + Cycle time. Time is calculated only within the set working days and hours. |
Mapped state | Mapped workflow state according to the workflow settings. Either Not started, In progress, or Done. |
Milestone | The project milestone the issue is assigned to. |
Moved to mapped state | Time when the item was moved to its current mapped workflow state. |
Moved to workflow state | Time when the item was moved to its current workflow state. |
Parent | Parent item of the issue (if any). |
Priority | The Priority of the issue. |
Project | The Project the issue is currently in. |
Reaction time | Time before the work was started. The time spent in the states mapped as Not started in the workflow settings. |
Reaction time (working hours) | Time before the work was started. The time spent in the states mapped as Not started in the workflow settings. Time is calculated only within the set working days and hours. |
Reopened | Whether the issue has been reopened (true/false) |
Started at | The time when the issue was started (from the Linear API) |
Started triage at | The time when the triage was started (from the Linear API) |
State | The issue workflow state |
State (open/done) | Whether the issue's mapped state is Open (Not started or In progress) or Done. |
Team | The team the issue is assigned to. |
Time in progress | The time spent in the states mapped as In progress in the workflow settings. |
Time in progress (working hours) | The time spent in the states mapped as In progress in the workflow settings. Time is calculated only within the set working days and hours. |
Time in workflow state | The time spent in the current workflow state. |
Timings | The total time spent in each workflow state. |
Triaged at | The time when the triage was completed (from the Linear API) |
Workflow state | The current workflow state of the issue. |
This page describes the available units, metrics, and issue properties when creating a chart for a Linear data source.
See also these related resources
Chart editor guide
Group and filter by label groups
Screenful Knowledge base
Units
Units are the numbers shown in the charts. Unit can be any of these:
Issue | The default unit is Issue i.e. a chart displays the count of issues and sub-issues. |
|---|---|
Estimates | Linear's default estimation field to describe the size of an issue. |
Time in state | Timing metrics (reaction, lead, cycle time). These are calculated for all issues and sub-issues. |
All units share these characteristics:
They can be filtered by any property of an issue
They can be summarized as sum, average, or median
They can be formatted as numbers, monetary units, or time units
Metrics
Metrics are the calculations performed on the selected unit.
Total | Shows the total amount of the selected unit in the selected data sources. |
|---|---|
Not started | Work not started according to the workflow settings. |
Not started & In progress | Incomplete work according to the workflow settings. |
In progress | Work in progress according to the workflow settings. |
Created (within date range) | Issues by creation date (issue creation date from the Linear API). |
Completed (within date range) | Issues by Date completed. The last date & time when the issue was completed (moved to a state mapped as done in the workflow settings). |
By Due date | Issues by Due date. Includes the items that have a Due date within the selected date range (regardless of their workflow state). |
Reaction time (avg, completed items) | Time before the work was started. The average time spent in the states mapped as Not started in the workflow settings. |
Reaction time (sum, completed items) | Time before the work was started. The sum of time spent in the states mapped as Not started in the workflow settings. |
Cycle time (avg, completed items) | Time from start to completion. The average time spent in the states mapped as In progress in the workflow settings. |
Cycle time (sum, completed items) | Time from start to completion The sum of time spent in the states mapped as In progress in the workflow settings. |
Lead time (avg, completed items) | Lead time (avg) = (Reaction time + Cycle time) (avg) |
Lead time (sum, completed items) | Lead time (sum) = (Reaction time + Cycle time) (sum) |
Time in state (avg, completed items) | Time spent in specific workflow states. Use the filter to select the states. |
Time in state (sum, completed items) | Time spent in specific workflow states. Use the filter to select the states. |
Issue properties
Issue properties that can be displayed as columns in a Task list.
Archived at | The time when the issue was archived. |
|---|---|
Assignee | The assigned person |
Assignees | The assigned persons (if multiple) |
Canceled at | The time when the issue was canceled. |
Completed on time | Was the item completed before the due date (true/false). |
Component | The Component the issue is currently assigned to. |
Created by | The person who created the issue. |
Cycle (assigned to) | The cycles the issue has been assigned to. |
Cycle (completed in) | The cycle the issue was completed in. |
Cycle time | Time from start to completion. The time spent in the states mapped as In progress in the workflow settings. |
Cycle time (working hours) | Time from start to completion. The time spent in the states mapped as In progress in the workflow settings. Time is calculated only within the set working days and hours. |
Data source | The Linear team the item is currently in. |
Date completed | The last date & time when the issue was completed (moved to a state mapped as done in the workflow settings). |
Date created | Item creation date (from the Linear API). |
Date updated | Last update date (from the Linear API) |
Due date | Issue Due date. |
Estimate | Linear's estimate field to describe the size of an issue. |
Issue ID | Unique identifier of the issue (from the Linear API). |
Issue name | Name of the issue. |
Item type | Issue or sub-issue. |
Label | The labels added to the issue. |
Lead time | Reaction time + Cycle time |
Lead time (working hours) | Reaction time + Cycle time. Time is calculated only within the set working days and hours. |
Mapped state | Mapped workflow state according to the workflow settings. Either Not started, In progress, or Done. |
Milestone | The project milestone the issue is assigned to. |
Moved to mapped state | Time when the item was moved to its current mapped workflow state. |
Moved to workflow state | Time when the item was moved to its current workflow state. |
Parent | Parent item of the issue (if any). |
Priority | The Priority of the issue. |
Project | The Project the issue is currently in. |
Reaction time | Time before the work was started. The time spent in the states mapped as Not started in the workflow settings. |
Reaction time (working hours) | Time before the work was started. The time spent in the states mapped as Not started in the workflow settings. Time is calculated only within the set working days and hours. |
Reopened | Whether the issue has been reopened (true/false) |
Started at | The time when the issue was started (from the Linear API) |
Started triage at | The time when the triage was started (from the Linear API) |
State | The issue workflow state |
State (open/done) | Whether the issue's mapped state is Open (Not started or In progress) or Done. |
Team | The team the issue is assigned to. |
Time in progress | The time spent in the states mapped as In progress in the workflow settings. |
Time in progress (working hours) | The time spent in the states mapped as In progress in the workflow settings. Time is calculated only within the set working days and hours. |
Time in workflow state | The time spent in the current workflow state. |
Timings | The total time spent in each workflow state. |
Triaged at | The time when the triage was completed (from the Linear API) |
Workflow state | The current workflow state of the issue. |
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.
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.
Yes, you can create charts with a prompt and ask questions about a chart by using the Screenful AI Assistant. The assistant combines the leading LLMs with advanced multidimensional data analytics to help you understand and interpret your data.
Yes, you can create charts with a prompt and ask questions about a chart by using the Screenful AI Assistant. The assistant combines the leading LLMs with advanced multidimensional data analytics to help you understand and interpret your data.
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.
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.
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.
Yes, you can create charts with a prompt and ask questions about a chart by using the Screenful AI Assistant. The assistant combines the leading LLMs with advanced multidimensional data analytics to help you understand and interpret your data.
Yes, you can create charts with a prompt and ask questions about a chart by using the Screenful AI Assistant. The assistant combines the leading LLMs with advanced multidimensional data analytics to help you understand and interpret your data.
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.
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.