Asana units, metrics, and properties
Asana units, metrics, and properties
This page describes the available units, metrics, and properties when creating a chart for an Asana data source.
See also these related guides
Chart editor guide
Creating charts using Asana custom fields
Screenful Knowledge base
Units
Units are the numbers shown in the charts. Unit can be any of these:
Task | The default unit is Task i.e. a chart displays the count of Tasks and subtasks. |
|---|---|
Number field | Any of your Number custom fields can be used as unit in the charts. |
Formula field | Formula fields can be used as unit in the charts as long as its value is a number. Learn more. |
Select field | Select and Multi-select fields can be mapped as units. |
Time in state | Timing metrics (reaction, lead, cycle time) are based on the time spent on a section or a custom field value. |
Estimated time | Estimated time to complete a task or subtask. |
Actual time | Time logged to a time tracking field. The date range refers to when the time was logged. |
All units share these characteristics:
They can be filtered by any property of an item
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) | Tasks by creation date (task creation date from the Asana API). |
Completed (within date range) | Tasks by Date completed. The last date & time when the item was completed (checked as done or moved to a state mapped as done) |
By Due date | Tasks by Due date (regardless of their status). Includes items that have the date within the specified date range. |
By Start date | Tasks by Start date (regardless of their status). Includes items that have the date within the specified date range. |
By [custom Date field] | Tasks by a custom Date field (regardless of their status). Includes items that have the date within the specified date range. |
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. |
Item properties
Item properties that can be displayed as columns in a Task list.
Actual time | Time logged to a time tracking field. |
|---|---|
Assignee | The assigned person |
Assignees | The assigned persons (if multiple) |
Completed on time | Was the task completed before the due date (true/false). |
Created by | The person who created the task. |
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 Asana project the item is currently in. |
Date completed | The last date & time when the task was completed (checked as done or moved to a state mapped as done). |
Date created | Task creation date (from the Asana API). |
Date updated | Last update date (from the Asana API) |
Due date | Due date of a task. |
Estimated time | Estimated time to complete a task. |
Item type | Either Item or Subitem. |
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. |
Moved to mapped state | The time when the item was moved to its current mapped workflow state. |
Moved to workflow state | The time when the item was moved to its current workflow state. |
Parent | Parent item of the item (if any) |
Portfolio | The Portfolio the task is currently assigned to. Portfolio is shown only if the user who did the authorization is the owner of the portfolio. |
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 task has been reopened (true/false) |
Section | The board section the task is currently in. If section is used as the workflow source, shows the current workflow state. |
Section (current) | The board section the task is currently in. If a task is moved to another section after its completion, this field shows the current section. |
Start date | Start date of a task, |
State (open/done) | Whether the task state is Open (Not started or In progress) or Done. |
Tag | Tags assigned to the task. |
Task ID | Unique identifier of the task (from the Asana API) |
Task name | Name of the task. |
Team | The team the task is assigned to. |
Time in progress | Time in progress so far. The time spent in the states mapped as In progress in the workflow settings. |
Time in progress (working hours) | Time in progress so far. 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 | How long the item has been in its current workflow state according to the workflow settings. |
Time logged by (Actual time) | Person who logged the hours into the time tracking field. |
Timings | How long the item has been in each workflow state according to the workflow settings. |
Workflow state | Workflow state according to the workflow settings. |
This page describes the available units, metrics, and properties when creating a chart for an Asana data source.
See also these related guides
Chart editor guide
Creating charts using Asana custom fields
Screenful Knowledge base
Units
Units are the numbers shown in the charts. Unit can be any of these:
Task | The default unit is Task i.e. a chart displays the count of Tasks and subtasks. |
|---|---|
Number field | Any of your Number custom fields can be used as unit in the charts. |
Formula field | Formula fields can be used as unit in the charts as long as its value is a number. Learn more. |
Select field | Select and Multi-select fields can be mapped as units. |
Time in state | Timing metrics (reaction, lead, cycle time) are based on the time spent on a section or a custom field value. |
Estimated time | Estimated time to complete a task or subtask. |
Actual time | Time logged to a time tracking field. The date range refers to when the time was logged. |
All units share these characteristics:
They can be filtered by any property of an item
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) | Tasks by creation date (task creation date from the Asana API). |
Completed (within date range) | Tasks by Date completed. The last date & time when the item was completed (checked as done or moved to a state mapped as done) |
By Due date | Tasks by Due date (regardless of their status). Includes items that have the date within the specified date range. |
By Start date | Tasks by Start date (regardless of their status). Includes items that have the date within the specified date range. |
By [custom Date field] | Tasks by a custom Date field (regardless of their status). Includes items that have the date within the specified date range. |
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. |
Item properties
Item properties that can be displayed as columns in a Task list.
Actual time | Time logged to a time tracking field. |
|---|---|
Assignee | The assigned person |
Assignees | The assigned persons (if multiple) |
Completed on time | Was the task completed before the due date (true/false). |
Created by | The person who created the task. |
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 Asana project the item is currently in. |
Date completed | The last date & time when the task was completed (checked as done or moved to a state mapped as done). |
Date created | Task creation date (from the Asana API). |
Date updated | Last update date (from the Asana API) |
Due date | Due date of a task. |
Estimated time | Estimated time to complete a task. |
Item type | Either Item or Subitem. |
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. |
Moved to mapped state | The time when the item was moved to its current mapped workflow state. |
Moved to workflow state | The time when the item was moved to its current workflow state. |
Parent | Parent item of the item (if any) |
Portfolio | The Portfolio the task is currently assigned to. Portfolio is shown only if the user who did the authorization is the owner of the portfolio. |
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 task has been reopened (true/false) |
Section | The board section the task is currently in. If section is used as the workflow source, shows the current workflow state. |
Section (current) | The board section the task is currently in. If a task is moved to another section after its completion, this field shows the current section. |
Start date | Start date of a task, |
State (open/done) | Whether the task state is Open (Not started or In progress) or Done. |
Tag | Tags assigned to the task. |
Task ID | Unique identifier of the task (from the Asana API) |
Task name | Name of the task. |
Team | The team the task is assigned to. |
Time in progress | Time in progress so far. The time spent in the states mapped as In progress in the workflow settings. |
Time in progress (working hours) | Time in progress so far. 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 | How long the item has been in its current workflow state according to the workflow settings. |
Time logged by (Actual time) | Person who logged the hours into the time tracking field. |
Timings | How long the item has been in each workflow state according to the workflow settings. |
Workflow state | Workflow state according to the workflow settings. |
This page describes the available units, metrics, and properties when creating a chart for an Asana data source.
See also these related guides
Chart editor guide
Creating charts using Asana custom fields
Screenful Knowledge base
Units
Units are the numbers shown in the charts. Unit can be any of these:
Task | The default unit is Task i.e. a chart displays the count of Tasks and subtasks. |
|---|---|
Number field | Any of your Number custom fields can be used as unit in the charts. |
Formula field | Formula fields can be used as unit in the charts as long as its value is a number. Learn more. |
Select field | Select and Multi-select fields can be mapped as units. |
Time in state | Timing metrics (reaction, lead, cycle time) are based on the time spent on a section or a custom field value. |
Estimated time | Estimated time to complete a task or subtask. |
Actual time | Time logged to a time tracking field. The date range refers to when the time was logged. |
All units share these characteristics:
They can be filtered by any property of an item
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) | Tasks by creation date (task creation date from the Asana API). |
Completed (within date range) | Tasks by Date completed. The last date & time when the item was completed (checked as done or moved to a state mapped as done) |
By Due date | Tasks by Due date (regardless of their status). Includes items that have the date within the specified date range. |
By Start date | Tasks by Start date (regardless of their status). Includes items that have the date within the specified date range. |
By [custom Date field] | Tasks by a custom Date field (regardless of their status). Includes items that have the date within the specified date range. |
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. |
Item properties
Item properties that can be displayed as columns in a Task list.
Actual time | Time logged to a time tracking field. |
|---|---|
Assignee | The assigned person |
Assignees | The assigned persons (if multiple) |
Completed on time | Was the task completed before the due date (true/false). |
Created by | The person who created the task. |
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 Asana project the item is currently in. |
Date completed | The last date & time when the task was completed (checked as done or moved to a state mapped as done). |
Date created | Task creation date (from the Asana API). |
Date updated | Last update date (from the Asana API) |
Due date | Due date of a task. |
Estimated time | Estimated time to complete a task. |
Item type | Either Item or Subitem. |
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. |
Moved to mapped state | The time when the item was moved to its current mapped workflow state. |
Moved to workflow state | The time when the item was moved to its current workflow state. |
Parent | Parent item of the item (if any) |
Portfolio | The Portfolio the task is currently assigned to. Portfolio is shown only if the user who did the authorization is the owner of the portfolio. |
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 task has been reopened (true/false) |
Section | The board section the task is currently in. If section is used as the workflow source, shows the current workflow state. |
Section (current) | The board section the task is currently in. If a task is moved to another section after its completion, this field shows the current section. |
Start date | Start date of a task, |
State (open/done) | Whether the task state is Open (Not started or In progress) or Done. |
Tag | Tags assigned to the task. |
Task ID | Unique identifier of the task (from the Asana API) |
Task name | Name of the task. |
Team | The team the task is assigned to. |
Time in progress | Time in progress so far. The time spent in the states mapped as In progress in the workflow settings. |
Time in progress (working hours) | Time in progress so far. 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 | How long the item has been in its current workflow state according to the workflow settings. |
Time logged by (Actual time) | Person who logged the hours into the time tracking field. |
Timings | How long the item has been in each workflow state according to the workflow settings. |
Workflow state | Workflow state according to the workflow settings. |
Learn more
Learn more
FAQ
Common questions
Screenful provides configurable charts and reports for Asana data, and tools to share that information with all stakeholders. Learn more about the supported metrics.
Screenful provides configurable charts and reports for Asana data, and tools to share that information with all stakeholders. Learn more about the supported metrics.
One data source is one Asana project. The pricing is based on the number of Asana projects you explicitly import to Screenful, not the total number of projects in Asana. 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.
One data source is one Asana project. The pricing is based on the number of Asana projects you explicitly import to Screenful, not the total number of projects in Asana. 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.
The timings are based on your workflow settings. You can learn more from the Lead Time FAQ.
The timings are based on your workflow settings. You can learn more from the Lead Time FAQ.
Yes, you can use the formula field as a unit in the charts. All formula fields are automatically imported. However, to make them available as a unit, you must ensure that the field is mapped to a unit in the custom fields mapping. Once it is mapped, it will be available in the unit menus. You can learn more from this guide.
Yes, you can use the formula field as a unit in the charts. All formula fields are automatically imported. However, to make them available as a unit, you must ensure that the field is mapped to a unit in the custom fields mapping. Once it is mapped, it will be available in the unit menus. You can learn more from this guide.
Yes, you can filter charts based on due dates or by status such as overdue. You can also track the work planned for the future using the Planned work chart. Learn more about setting up the chart for Asana.
Yes, you can filter charts based on due dates or by status such as overdue. You can also track the work planned for the future using the Planned work chart. Learn more about setting up the chart for Asana.
Yes. You can use a custom field for entering an estimate to a task. Learn more about how to set estimates for your tasks in Asana.
Yes. You can use a custom field for entering an estimate to a task. Learn more about how to set estimates for your tasks in Asana.
Archived tasks are treated differently depending on whether they are completed or not. Completed tasks are still considered completed even if they are archived. Tasks that are archived before they were completed are considered removed.
Archived tasks are treated differently depending on whether they are completed or not. Completed tasks are still considered completed even if they are archived. Tasks that are archived before they were completed are considered removed.
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
Screenful provides configurable charts and reports for Asana data, and tools to share that information with all stakeholders. Learn more about the supported metrics.
Screenful provides configurable charts and reports for Asana data, and tools to share that information with all stakeholders. Learn more about the supported metrics.
One data source is one Asana project. The pricing is based on the number of Asana projects you explicitly import to Screenful, not the total number of projects in Asana. 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.
One data source is one Asana project. The pricing is based on the number of Asana projects you explicitly import to Screenful, not the total number of projects in Asana. 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.
The timings are based on your workflow settings. You can learn more from the Lead Time FAQ.
The timings are based on your workflow settings. You can learn more from the Lead Time FAQ.
Yes, you can use the formula field as a unit in the charts. All formula fields are automatically imported. However, to make them available as a unit, you must ensure that the field is mapped to a unit in the custom fields mapping. Once it is mapped, it will be available in the unit menus. You can learn more from this guide.
Yes, you can use the formula field as a unit in the charts. All formula fields are automatically imported. However, to make them available as a unit, you must ensure that the field is mapped to a unit in the custom fields mapping. Once it is mapped, it will be available in the unit menus. You can learn more from this guide.
Yes, you can filter charts based on due dates or by status such as overdue. You can also track the work planned for the future using the Planned work chart. Learn more about setting up the chart for Asana.
Yes, you can filter charts based on due dates or by status such as overdue. You can also track the work planned for the future using the Planned work chart. Learn more about setting up the chart for Asana.
Yes. You can use a custom field for entering an estimate to a task. Learn more about how to set estimates for your tasks in Asana.
Yes. You can use a custom field for entering an estimate to a task. Learn more about how to set estimates for your tasks in Asana.
Archived tasks are treated differently depending on whether they are completed or not. Completed tasks are still considered completed even if they are archived. Tasks that are archived before they were completed are considered removed.
Archived tasks are treated differently depending on whether they are completed or not. Completed tasks are still considered completed even if they are archived. Tasks that are archived before they were completed are considered removed.
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
Below are some typical reasons for charts not displaying the data you expect:
Your data hasn't loaded yet. When the data sync process is in progress, a spinner icon is displayed at the top right of the UI. When you hover the mouse over the icon, you can see the progress.
The chart shows data based on a different field than what you think. Learn more about selecting items for a chart.
Your workflow mapping is not done correctly. You can learn more about workflow mapping from this guide. Notice that the cards that are in lists mapped to Excluded won't be imported to Screenful.
Your board is not connected. If a data source is not connected, you'll see a red notification on the top right of the UI. Click the notification icon to re-authorize the data source.
Below are some typical reasons for charts not displaying the data you expect:
Your data hasn't loaded yet. When the data sync process is in progress, a spinner icon is displayed at the top right of the UI. When you hover the mouse over the icon, you can see the progress.
The chart shows data based on a different field than what you think. Learn more about selecting items for a chart.
Your workflow mapping is not done correctly. You can learn more about workflow mapping from this guide. Notice that the cards that are in lists mapped to Excluded won't be imported to Screenful.
Your board is not connected. If a data source is not connected, you'll see a red notification on the top right of the UI. Click the notification icon to re-authorize the data source.
I have created an automation to move completed tasks from one Asana board to another. Will that mess up my stats?
If a task is moved from Project A to Project B, you will lose the task history from Project A since the Asana API won't return it anymore. Instead of moving to another project, you can create a dedicated "Archived" section at the bottom of your project (that is folded by default), and set up an automation to move completed tasks to that section instead of another project. That way, you won't lose any history.
If a task is moved from Project A to Project B, you will lose the task history from Project A since the Asana API won't return it anymore. Instead of moving to another project, you can create a dedicated "Archived" section at the bottom of your project (that is folded by default), and set up an automation to move completed tasks to that section instead of another project. That way, you won't lose any history.
When you are importing projects, you are shown all the projects of the teams in which you are a member. In order to see more projects, add yourself to the respective teams.
When you are importing projects, you are shown all the projects of the teams in which you are a member. In order to see more projects, add yourself to the respective teams.
You may not see all the portfolios due to a restriction in the Asana API. Portfolios are shown only if the user who did the authorization is the owner of the portfolios.
You may not see all the portfolios due to a restriction in the Asana API. Portfolios are shown only if the user who did the authorization is the owner of the portfolios.
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
Below are some typical reasons for charts not displaying the data you expect:
Your data hasn't loaded yet. When the data sync process is in progress, a spinner icon is displayed at the top right of the UI. When you hover the mouse over the icon, you can see the progress.
The chart shows data based on a different field than what you think. Learn more about selecting items for a chart.
Your workflow mapping is not done correctly. You can learn more about workflow mapping from this guide. Notice that the cards that are in lists mapped to Excluded won't be imported to Screenful.
Your board is not connected. If a data source is not connected, you'll see a red notification on the top right of the UI. Click the notification icon to re-authorize the data source.
Below are some typical reasons for charts not displaying the data you expect:
Your data hasn't loaded yet. When the data sync process is in progress, a spinner icon is displayed at the top right of the UI. When you hover the mouse over the icon, you can see the progress.
The chart shows data based on a different field than what you think. Learn more about selecting items for a chart.
Your workflow mapping is not done correctly. You can learn more about workflow mapping from this guide. Notice that the cards that are in lists mapped to Excluded won't be imported to Screenful.
Your board is not connected. If a data source is not connected, you'll see a red notification on the top right of the UI. Click the notification icon to re-authorize the data source.
I have created an automation to move completed tasks from one Asana board to another. Will that mess up my stats?
If a task is moved from Project A to Project B, you will lose the task history from Project A since the Asana API won't return it anymore. Instead of moving to another project, you can create a dedicated "Archived" section at the bottom of your project (that is folded by default), and set up an automation to move completed tasks to that section instead of another project. That way, you won't lose any history.
If a task is moved from Project A to Project B, you will lose the task history from Project A since the Asana API won't return it anymore. Instead of moving to another project, you can create a dedicated "Archived" section at the bottom of your project (that is folded by default), and set up an automation to move completed tasks to that section instead of another project. That way, you won't lose any history.
When you are importing projects, you are shown all the projects of the teams in which you are a member. In order to see more projects, add yourself to the respective teams.
When you are importing projects, you are shown all the projects of the teams in which you are a member. In order to see more projects, add yourself to the respective teams.
You may not see all the portfolios due to a restriction in the Asana API. Portfolios are shown only if the user who did the authorization is the owner of the portfolios.
You may not see all the portfolios due to a restriction in the Asana API. Portfolios are shown only if the user who did the authorization is the owner of the portfolios.
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.