Project management
.png)
Bring your tasks in context with OKRs with Jira and Tability
Easily connect to all of your apps using Zapier, and create check-ins on your goals and OKRs automatically.
Quite often businesses start by just trying things and seeing what works. It's very output-driven. A long list of tickets and tasks, with a never ending backlog. It's messy but it works, you you're at a stage where you just need to try stuff.
As your startup or scale-up grows, and you start to see what works, you need to find a harmonious balance between how much you focus on outcomes as well as outputs. Outcomes (measured with OKRs) are what we use to understand where we are headed, and outputs (tasks and projects) are what we use to get there. The OKRs give a 'why' to the tasks you're doing.
Tasks and projects aren't always mentioned in the world of OKRs, but the two things go hand in hand. Your OKRs help inform decisions on what tasks you should be working on, and completing the tasks drive your progress. Completing tasks and seeing the results then informs whether your goalposts were in the right place, and you can adjust your OKRs or strategy accordingly.
.png)
Teams like Rebill use Tability to help them make sense of their Jira tasks. We know what we're suppose to work on, but their OKRs in Tability help them understand the bigger picture and the why behind those tasks:
Before Tability, everything was pretty much planned and executed through Jira. Because of how seamlessly Tability integrates with Jira, bringing their Jira tickets into Tability and their OKRs into Jira was seamless. Nahuel says, “It was a perfect fit to drop into the technical team to start using. It allows you to track how far you are from the goal that you proposed at the very beginning of the quarter.”
Tability's seamless integration makes it easy to understand the connections between OKR and task.
Learn more about how to connect your Jira tickets to Tability OKRs below.
There are three main features that are included natively to connect with Jira in Tability:
How do tasks work in Tability?
Tability makes it easy to add Jira tickets into your OKRs as tasks. All you have to do is copy paste the link as a task!
By doing this, you'll always see what Jira tickets are related to specific key results and understand the context between tasks and results at all times.
Let's be real, your development team probably isn't going to spend a ton of time thinking about their OKRs. They're busy crushing tickets and writing code. That's why it's important that when you add a Jira ticket to your OKRs in Tability, it will display your related key results in your Jira ticket as well.
Now your dev team never has to leave Jira. They understand the progress toward their relevant KRs right in context to their work.
Last but not least, Tability's integration also let's you connect to data points in Jira to automate check-ins in Tability.
You can use Jira as a data source to automatically pull the number of Jira issues corresponding to a specific JQL request. This becomes extremely useful when you're tracking ticket requests and activity as an OKR.
Setting up this integration is easy and only takes a few steps.
Installing the Tability app in Jira:
For more info on how to connect Jira to Tability, check out the Tability guides.
Managing OKRs can be a hassle when your data is scattered across different tools. Pulling performance metrics or progress updates from various platforms is time-consuming and repetitive. Worse yet, you end up duplicating work—updating your OKRs in one place and entering the same data elsewhere. It’s a frustrating cycle that slows you down and distracts from focusing on results.
More often than not, this just leads to teams not updating their OKRs and letting them collect dust. It's just too cumbersome and distracting from the task at hand.
That's why teams trust Tability. Tability makes this part easy, by bringing all of your data into one place.
Using data connectors you can pull data from the apps where you do your work and where you collect data.
Using Tability data connectors, you can have live data in your OKRs at all times. Once you add your data connector as a data source for an outcome/Key Result, Tability can:
Example:
Once you have your data sources connected, you can enable auto-sync on your key results. What this does is it automatically creates check-ins on your Key Results so that you have the latest data in Tability at all times.
Connecting your data connectors to Tability is easy and takes only a few minutes:
For more info on how to set up data connectors and how they work, visit our user guide.
See an up-to-date status of the OKRs linked to a specific Jira ticket—without leaving Jira.
Mention issues in your check-ins to link them to your goals. See all issues related, with their accurate status.
Automate check-ins by connecting to data points via Zapier. Every time an action is performed in one of your apps, Tability creates a check-in for you!
Where are we now, and how far do we have to go? Tability shows you the entire journey, compared to your progress in real time.
Adding your analysis helps your team understand the numbers, and fosters conversations to start around what’s most important in your org.
.png)
Bring your tasks in context with OKRs with Jira and Tability
Easily connect to all of your apps using Zapier, and create check-ins on your goals and OKRs automatically.
Seamlessly integrate your OKRs into your workflow.