With Shotgun Production Insights, you can create generic time series and status history graphs, including burndown charts.
The examples below represent the status history of Tasks in a project over time, and a burndown of the number of Tasks left to complete in a project over time.
To learn how to set up other types of graphs, please see our graph widget tutorial.
You can easily graph things over time using the “Timeline” sorting mode to graph based on any
date_time field. The first graph in the example below displays Tasks that are due per week, and the second graph displays time logged per week, to make it easy to compare.
To create your own “Due Tasks per Week” graph, choose the Task entity and graph by “Due Date,” by week. Then choose to sort by “Timeline.”
The “Status History Graph” widget gives you the ability to graph status changes over time and see the progression. This widget can display data from your site. Your Shotgun site collects data every time someone updates a status. Shotgun has been collecting status changes since the Shotgun 7.10 release, which means you will have access to historical data from Shotgun 7.10 and onward.
Note: The “Status History Graph” is only about status. You can only select entities that have at least one status field, and you can only graph on status fields.
Depending on the volume of the data you are graphing, Shotgun will return either hourly, daily, or weekly status change information, to optimize graph rendering times. Therefore, if a status changes multiple times in the returned period, you will only see the last status change of that period.
For large data sets, for example data spanning one year or longer, Shotgun will automatically group your data on the backend. This is to ensure that the graph displays data in a digestible way. Therefore, the larger your range of data, the less granularity you will see.
Below is an example of a Task Status History graph, to show the number of days you have to finish Tasks. Note that “Mode” is set to “History” and “Show” is set to “Sum.” Additionally, the Project Timeline Range is set to display the start and end dates, which are taken from your project or the entity you are graphing on. The start and end dates are reflected in the bar handles at the bottom of the graph (in white). The graph is automatically zoomed in, and you can also zoom in and out of the graph.
When creating a graph in “History” or “Burndown” mode, note that the options for showing a summary on a bid or any other field have been simplified.
Burndown charts display how much work is left to do over a period of time. This type of graph may help you with scheduling, as you can see how many Tasks are left for your artists. You can also use this type of graph to display the sum of Bid days or the sum or any numerical field, by using the “Show: Sum” option.
The example below represents Tasks that must still be completed over the course of the project, based on phases in the project.
You can create this graph, and all graphs, by designing your canvas page and adding the graph widget. The example above uses the “Status History Graph” widget.
Choose to graph by the Task entity, and then use the following options:
- “Burndown” for “Mode”
- “Final” for “Done Status” (to exclude the “fin” status from your graph)
- “Count” for “Show”
You can also choose to display a dotted “Goal Line” to see your target goal.
Note: You can only choose the “Goal Line” option in “Burndown” mode and when you have the start and end date in your timeline range. This line is drawn using the total amount from the start date of your range to a target of “0” on the end date.
You can graph using the “Project Timeline Range” functionality or the “Timeline Range” of another entity. This functionality will automatically zoom in on the selected Timeline range, and is used to draw the “Goal Line” in “Burndown” mode.
To graph a global burndown, you can create the graph on any canvas page and take advantage of the “Project Timeline Range.” To graph the “Timeline Range” on a specific entity, you will need to design your graph from that entity’s detail page.
For example, you can create a graph that displays data around a release. To do this, go to a release detail page, and design your graph from there.
To graph on a Phase, go to the Phase page. Then click on one of the phases, and view it on the detail page mode. You’ll see the option of the Phase timeline range. This burndown graph can be done on the context of any entity (release, shot, sequence, custom entity, etc.). It works best for entities you need to track with start and end dates.
Note: When graphing time, you have the option to display phases and milestones.
When you display the project, the bars at the beginning and end indicate the start and end dates of the project. The sprints within the graph are phases. You can also choose to display milestones.
If you see the error message, “This graph contains a large amount of data and the request takes too long to return. Please reduce the amount of data by updating your filters.”, it means you will need to reduce the amount of data to graph in order for it to render.