TL;DR
During Sprint 20, the team started working on a new home page. This project will take multiple sprints to complete, but it will provide our customers with a summary view of three important questions: What are we building? When will it be done? How much will it cost?
Additionally, in this sprint, the team focused on improving the transparency and flexibility of our calculations to answer these questions.
Sprint goal
The goal for this sprint was to establish a page in production (turned off) that contains the "wrapper" elements in the header and left nav. These will ultimately serve the entire application.
- We’ve started building out a new home page! We’re excited to share this with you soon. So far, we’ve shipped (but not enabled) the header and navigation menu, preparing these areas for the new features on the way.
- We’re also adding a global message center to the header so that we can alert you when big changes are coming, or when maintenance windows are necessary. This will debut when the rest of the new home page is ready.
- Finally, we’ve shipped (but not yet enabled) an FAQ section from the new header as the first leg of our upcoming knowledge base. We know process intelligence is not the easiest thing out of the box, so we’re working towards getting your questions asked & answered as easy as possible, partnering with our Customer Success team and Early Adopters!
Updates
- Improved our security by converting our database keys to UUID. This creates a more secure URL string for our customers.
- Scaled our configuration capabilities to the sub-project level. With this enhancement, our customers can be onboarded beyond the project level to the sub-project level (common Jira terms). A good example of this would be tracking a Design board separately from a Development board for the same product.
- Added contact details to server error pages to help stranded customers get a hand from our Customer Success team!
What we fixed
- This sprint, we fixed the precision of our cycle time calculations using time graphs so that we correctly capture the beginning and completion of a task.
