LiveView enables you to track the delivery of your work across the entire toolchain to better understand how you're progressing toward your goals and, most importantly, where things might be going off course.

We continuously analyse your tickets' progress throughout the toolchain and compare it to your historical patterns in order to proactively highlight potential concerns, called Action Items. These Action Items enable you to get ahead of any issues that may put your goals at risk.

(LiveView supports sprints initially, but it will be developed further to look at other attributes such as epics and fix versions in due course).

How to enable LiveView

To enable LiveView, go into your workspace settings, click the LiveView enabled button and click Save Changes.

It's important to note that your historical thresholds are based on the data sources configured for the workspace, i.e. the board, repos, pipelines etc. So do make sure you double check these settings as well to ensure we are comparing apples to apples.

Using LiveView

LiveView will display in the left navigation above your dashboards

You will now be able to view all tickets assigned to the sprint and see all of the updates made to that ticket throughout all of the toolsets you have connected with Plandek.

You can apply ticket filters to drill down further if required. The filters allow you to look at different issue types (such as a story) or tickets in a certain status (such as "In Development"). You can also switch the toggle on or off to only see tickets with an action item.

A chart at the top of the screen shows the current statuses of the tickets in the sprint cycle, so you can visualise the progress of your tickets too.

Action Items

Action Items are displayed against the tickets to highlight issues that you may want to look into further. There are four types of action items which are listed below. For further details on what the action items could mean please read our FAQs here: -

Code Cycle Time: An important indication of how long a pull request has been in a certain state, or how long it has taken to be merged.

Complexity: A useful indication of how complex a piece of work is from an engineering perspective, based on files changes, developers involved, and repos touched.

Delivery Time: Highlights any ticket that has spent more time in a status than usual, or has taken longer overall to deliver.

Work Added / Change to sprint scope: Highlights any unplanned tickets that have made their way into the sprint.

Did this answer your question?