
The Ultimate Jira Dashboard
Accurate burn-down charts based on all linked issue points. See which issues moved - where they were, and where they went. Drill down to get story details. Compare multiple sprints. Single click access to issues in Jira.
See @mentions for each person so you don't miss stray comments that become inadvertent blockers. Hover over the Jira IDs to get summary details. It's a quick way to monitor who needs to do what to stay on schedule.
No more slogging through seemingly endless Jira notifications. Select the Jira properties (including custom) that you want to be alerted about when changes happen. Alerts roll up from linked stories to Epics.
Accurate burn-down charts based on all linked issue points. See which issues moved - where they were, and where they went. Drill down to get story details. Compare multiple sprints. Single click access to issues in Jira.
See @mentions for each person so you don't miss stray comments that become inadvertent blockers. Hover over the Jira IDs to get summary details. It's a quick way to monitor who needs to do what to stay on schedule.
No more slogging through seemingly endless Jira notifications. Select the Jira properties (including custom) that you want to be alerted about when changes happen. Alerts roll up from linked stories to Epics.
More details
Ever had sprints go off the rails? It's painful. Unfinished stories, estimate changes, last-minute additions. Jira does a great job managing tasks. But you need a top-down view to quickly understand what is really going on to keep sprints on track.
That’s why we built Obo Tracker. It give you the big picture:
- Are we really on schedule? Know immediately with sprint burndown charts that roll up issue points under Epics
- Which critical issue properties changed? Get alerts for just the changes you care most about
- What is blocked? See comment mentions and issues assigned to you and your team that are impeding progress
- What moved? See when issues moved, where they were, and where they went
- What is not getting worked on? Discover issues that get opened but not finished
- How do I keep Execs informed? Share Obo Tracker so they get the big picture too
And much more. Setup takes less than a minute. Try it with your data or our demo data – no risk. Click here to learn more and get a free trial.
More details
Ever had sprints go off the rails? It's painful. Unfinished stories, estimate changes, last-minute additions. Jira does a great job managing tasks. But you need a top-down view to quickly understand what is really going on to keep sprints on track.
That’s why we built Obo Tracker. It give you the big picture:
- Are we really on schedule? Know immediately with sprint burndown charts that roll up issue points under Epics
- Which critical issue properties changed? Get alerts for just the changes you care most about
- What is blocked? See comment mentions and issues assigned to you and your team that are impeding progress
- What moved? See when issues moved, where they were, and where they went
- What is not getting worked on? Discover issues that get opened but not finished
- How do I keep Execs informed? Share Obo Tracker so they get the big picture too
And much more. Setup takes less than a minute. Try it with your data or our demo data – no risk. Click here to learn more and get a free trial.
Reviews for cloud
(3)Sign in to write a review
Reviews for server
(3)Sign in to write a reviewReviews for Data Center
(3)Sign in to write a reviewCloud Pricing
Server Pricing
Data Center Pricing
This app is sold by a third-party vendor.
Let us know that you'd like to manage this app's billing on your Atlassian invoice.This app is sold by a third-party vendor.
Contact the vendor to evaluate or purchase this app.Pricing FAQ
- What does 'paid-via-vendor' mean?
Paid-via-vendor apps are licensed and purchased directly through the vendor who makes this app.
Payment for paid-via-vendor apps is not handled by Atlassian.
- Will paid-via-vendor transactions be on my Atlassian invoice?
Paid-via-vendor transactions are not managed by Atlassian. This means transactions for paid-via-vendor apps will not be on your Atlassian invoice.
Pricing FAQ
- What does 'paid-via-vendor' mean?
Paid-via-vendor apps are licensed and purchased directly through the vendor who makes this app.
Payment for paid-via-vendor apps is not handled by Atlassian.
- Will paid-via-vendor transactions be on my Atlassian invoice?
Paid-via-vendor transactions are not managed by Atlassian. This means transactions for paid-via-vendor apps will not be on your Atlassian invoice.
Obo.pm provides support for this app.
Obo.pm provides support for this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Jira Cloud • Released 2021-02-15
Summary
Added individual team member selection, single sign-on, and Jira Server support.
Versions
Version 2.0 • Jira Server 7.0.0 - 8.15.0 • Released 2021-02-15
Summary
Added individual team member selection, single sign-on, and Jira Server support.
Installation
- [1] Click here to sign up for a free trial. [2] Use our Jira demo data for a test drive, or connect to your Jira instance. The program will guide you through the steps - it usually takes less than a minute (learn more about connecting to Jira here). [3] Obo Tracker does the rest. Within a few minutes, you will have a complete view of your sprints - at a level that matters to you.
- [1] Click here to sign up for a free trial. [2] Use our Jira demo data for a test drive, or connect to your Jira instance. The program will guide you through the steps - it usually takes less than a minute (learn more about connecting to Jira here). [3] Obo Tracker does the rest. Within a few minutes, you will have a complete view of your sprints - at a level that matters to you.