You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
As a Senior Product Manager at Devbridge, I create bespoke products for multiple customers in many different types of industries such as Agriculture, Fintech, Finance, etc. Naturally, here at Devbridge, we use all the Atlassian suite of products in the Cloud. As an Atlassian expert (I worked at Adaptavist creating products for the Atlassian ecosystem), I couldn’t help but notice that even though we make extensive use of Jira to manage our customers’ products, we didn’t use it much for internal reporting. Instead, we were using Google Spreadsheets to track the status of each of our customers/projects.
This is just a small snapshot of a lengthy spreadsheet that requires users to scroll down and down and down and also from left to right, on and on.
This solution was not great because:
One of our core values at Devbridge is “Taking Ownership,” so I decided to take matters into my own hands and create a solution that was user-friendly, allowed data to be filtered, and reported, promoting collaboration.
I embarked on a way to convert this messy process into a much more robust, transparent solution. I used Jira Cloud for it. Why Jira? It allowed me to convert and customize the data in this massive Excel spreadsheet—quickly and easily.
Using Jira, I created Project Health Report. The idea was to convert all of the long scrolling spreadsheet rows into a Jira tickets. Each Risk would be a sub-task of the ticket as seen below.
BOOM! All of the problems were fixed with this simple solution—Jira!
Another cool feature included dashboards. These dashboards were generated quickly, allowing the team to have shared visibility to the overall project status. To improve upon this in future iterations, we would use ScriptRunner for Jira to automate the majority of these custom fields calculations. (Another next step is to add in forecasting, but that's a topic for another article. )
I honestly believe that most internal process issues can be solved using Jira, not Google Spreadsheets. Jira offers much more robust project reporting. So if you wish to migrate away from the information-heavy spreadsheet toward a better business process, while also increasing collaboration and above all making work much more fun, I strongly believe that Jira Cloud is the right solution. (Remember the spreadsheet example above that was not user-friendly or easily searchable, was hard to customize, and had version control issues? Not fun.)