Schedule via email or Slack
Schedule via email or Slack
In addition to viewing a report or downloading it as PDF, reports can be shared via email and Slack on a custom schedule, or with a share link.
In addition to viewing a report or downloading it as PDF, reports can be shared via email and Slack on a custom schedule, or with a share link.
In addition to viewing a report or downloading it as PDF, reports can be shared via email and Slack on a custom schedule, or with a share link.
Sending a sample report
Before you schedule a report to be sent automatically at the set schedule, you may want to send a sample report to selected recipients for review. To trigger one-time sending, click the three dots next to any of the reports in the list and select Schedule from the menu.
The scheduling view is opened, allowing you to select the recipients from the list (you can add more users by inviting them first).
Once you click Send to selected users, the report is immediately sent via email to the selected users.
Sending a sample report
Before you schedule a report to be sent automatically at the set schedule, you may want to send a sample report to selected recipients for review. To trigger one-time sending, click the three dots next to any of the reports in the list and select Schedule from the menu.
The scheduling view is opened, allowing you to select the recipients from the list (you can add more users by inviting them first).
Once you click Send to selected users, the report is immediately sent via email to the selected users.
Scheduling a report to be sent via email
To schedule a report, click the three dots next to any of the reports in the list and select Schedule from the menu.
The scheduling view is opened, which allows you to select the frequency (daily/weekly/monthly), and the time of day when the report will be sent.
Once the schedule is saved, the report will be emailed to the selected recipients according to the set schedule. The message contains a link to the live report online, and the PDF export as an attachment.
When you click the attachment, the report is shown:
Once a report is scheduled, it is saved in the archive so you can review any previous state of your project. You can access the archive by selecting View previous reports from the same three-dot menu.
Scheduling a report to be sent via email
To schedule a report, click the three dots next to any of the reports in the list and select Schedule from the menu.
The scheduling view is opened, which allows you to select the frequency (daily/weekly/monthly), and the time of day when the report will be sent.
Once the schedule is saved, the report will be emailed to the selected recipients according to the set schedule. The message contains a link to the live report online, and the PDF export as an attachment.
When you click the attachment, the report is shown:
Once a report is scheduled, it is saved in the archive so you can review any previous state of your project. You can access the archive by selecting View previous reports from the same three-dot menu.
Scheduling a report to be sent to Slack
You can schedule any of your reports to be sent to a chosen Slack channel. To get started, follow the instructions in this guide to set up the Slack integration.
Reports can be scheduled to be sent to Slack in the same Schedule report page, which allows setting the schedule for the report. You can access this page by selecting Schedule from the report context menu.
On the report schedule page, you can select the Slack channel to send the report to:
Once you click Save changes, the report will be sent to the selected Slack channel at the scheduled frequency. Here’s the report in Slack.
The message contains a link to the live report online and the PDF export. When you click the PDF preview, the report is opened within the Slack UI.
Scheduling a report to be sent to Slack
You can schedule any of your reports to be sent to a chosen Slack channel. To get started, follow the instructions in this guide to set up the Slack integration.
Reports can be scheduled to be sent to Slack in the same Schedule report page, which allows setting the schedule for the report. You can access this page by selecting Schedule from the report context menu.
On the report schedule page, you can select the Slack channel to send the report to:
Once you click Save changes, the report will be sent to the selected Slack channel at the scheduled frequency. Here’s the report in Slack.
The message contains a link to the live report online and the PDF export. When you click the PDF preview, the report is opened within the Slack UI.
Sharing reports with a share link
In addition to sharing via email or by sending to Slack, you can also share reports with a link.
To get a link, go to the Reports tab and locate the report that you want to share a link to (if you’re within a dashboard, you can get to this view by selecting exit dashboard under the main menu).
The share feature can be found in the report context menu.
When you select Share, a modal shown and the share link is copied to the clipboard. You can send the link and the recipient can view the report by following the link.
If you want to share the report with someone who doesn’t have a Screenful account, you can reveal more options by clicking the Make this a public link.
If you check the Enable public sharing checkbox, the link is made public so that anyone can follow the link and see the report in read-only mode.
While the link has a random character sequence so that it’s not possible to guess the link, anyone with the link can access the chart. Share the link only with people who you would like to see the data.
You can disable the link anytime by unchecking the Enable public sharing checkbox. If you disable a share link, it will be disabled permanently. If you enable sharing again, a new share link is generated, and the previously shared link remains disabled.
Sharing reports with a share link
In addition to sharing via email or by sending to Slack, you can also share reports with a link.
To get a link, go to the Reports tab and locate the report that you want to share a link to (if you’re within a dashboard, you can get to this view by selecting exit dashboard under the main menu).
The share feature can be found in the report context menu.
When you select Share, a modal shown and the share link is copied to the clipboard. You can send the link and the recipient can view the report by following the link.
If you want to share the report with someone who doesn’t have a Screenful account, you can reveal more options by clicking the Make this a public link.
If you check the Enable public sharing checkbox, the link is made public so that anyone can follow the link and see the report in read-only mode.
While the link has a random character sequence so that it’s not possible to guess the link, anyone with the link can access the chart. Share the link only with people who you would like to see the data.
You can disable the link anytime by unchecking the Enable public sharing checkbox. If you disable a share link, it will be disabled permanently. If you enable sharing again, a new share link is generated, and the previously shared link remains disabled.
Learn more
Learn more
FAQ
Common questions
A data source is a GitLab board. The pricing is based on the number of boards you explicitly import to Screenful, not the total number of boards in GitLab. 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 GitLab board. The pricing is based on the number of boards you explicitly import to Screenful, not the total number of boards in GitLab. 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.
Yes except that you won’t be able to use data from epics or issue weights since those are available only in a paid GitLab plans.
Yes except that you won’t be able to use data from epics or issue weights since those are available only in a paid GitLab plans.
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 filter the data shown so that either issues, merge requests, or both are included in the stats by setting a filter.
Yes, you can filter the data shown so that either issues, merge requests, or both are included in the stats by setting a filter.
Yes, you can track GitLab epics with Screenful. You can use "Epic" as a filter in a chart. For the chart that supports grouping (bar charts, pie chart, stacked area chart), you can group data by epic. You can also filter charts by "Item type"->"Epic". That will include only epics in the chart.
Yes, you can track GitLab epics with Screenful. You can use "Epic" as a filter in a chart. For the chart that supports grouping (bar charts, pie chart, stacked area chart), you can group data by epic. You can also filter charts by "Item type"->"Epic". That will include only epics in the chart.
Yes, you can group and filter data by iterations. You can also create a burndown chart for tracking a Gitlab iteration.
Yes, you can group and filter data by iterations. You can also create a burndown chart for tracking a Gitlab iteration.
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 GitLab board. The pricing is based on the number of boards you explicitly import to Screenful, not the total number of boards in GitLab. 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 GitLab board. The pricing is based on the number of boards you explicitly import to Screenful, not the total number of boards in GitLab. 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.
Yes except that you won’t be able to use data from epics or issue weights since those are available only in a paid GitLab plans.
Yes except that you won’t be able to use data from epics or issue weights since those are available only in a paid GitLab plans.
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 filter the data shown so that either issues, merge requests, or both are included in the stats by setting a filter.
Yes, you can filter the data shown so that either issues, merge requests, or both are included in the stats by setting a filter.
Yes, you can track GitLab epics with Screenful. You can use "Epic" as a filter in a chart. For the chart that supports grouping (bar charts, pie chart, stacked area chart), you can group data by epic. You can also filter charts by "Item type"->"Epic". That will include only epics in the chart.
Yes, you can track GitLab epics with Screenful. You can use "Epic" as a filter in a chart. For the chart that supports grouping (bar charts, pie chart, stacked area chart), you can group data by epic. You can also filter charts by "Item type"->"Epic". That will include only epics in the chart.
Yes, you can group and filter data by iterations. You can also create a burndown chart for tracking a Gitlab iteration.
Yes, you can group and filter data by iterations. You can also create a burndown chart for tracking a Gitlab iteration.
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
Screenful connects to the GitLab board, not a project or group, so the first thing would be to check that the missing issues or pull requests are visible on that board.
Screenful connects to the GitLab board, not a project or group, so the first thing would be to check that the missing issues or pull requests are visible on that board.
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
Screenful connects to the GitLab board, not a project or group, so the first thing would be to check that the missing issues or pull requests are visible on that board.
Screenful connects to the GitLab board, not a project or group, so the first thing would be to check that the missing issues or pull requests are visible on that board.
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.