For OBoard (OKR), can you link sprints (instead of issues/epics) to the Key Results ?

[Hen Huynh]

As it is intuitive to deliver key results from sprints, is there a way to link a sprint to a key result (instead of issues/epics) ?

[Margo Sakova - OKR Board for Jira by Oboard · Accepted solution]

Hi @Hen Huynh!

I totally get it – adding each issue one by one can be a bit of a hassle, especially when there's a bunch of them. My suggestion is to link all the issues in your sprint at once using JQL.

 Here's a quick guide:

1. Click on the Key Result where you want to link your sprint and select "Link Jira Issue."

2. Opt for "JQL" right under "Link Jira Issue."

3. Type your Sprint Name in JQL with the query sprint='SPRINT NAME'
   Then hit "Search" to find all related issues and "Link" to attach them to your Key Result.

Let me know if you want more tips and tricks for using the Oboard app. I'd love to schedule a demo for you

[Hen Huynh]

Thank you @Margo Sakova - OKR Board for Jira by Oboard

worked like a charm !

[Margo Sakova - OKR Board for Jira by Oboard]

Happy to help 😊

[Sing Chen]

@Margo Sakova - OKR Board for Jira by Oboard  I've just come across this conversation and I'm curious, is the JQL method for linking jira issues dynamic? By that I mean, if new issues come into the scope of the JQL query, would they be automatically appear linked to the KR?

When I think about how our business runs, we would link epics under a particular initiative to a KR. However, as progress is made on delivering the initiative, new epics could appear or existing epics could be cancelled and having the list of epics dynamically update under the KR based on the JQL would be hugely powerful.

Thanks,

Sing

[Margo Sakova - OKR Board for Jira by Oboard]

Hi @Sing Chen

As I understood, your initiatives stay the same, but the epics underneath can be changed. For this case, the easiest solution would be to link the initiatives directly to the Key Results. This way, the child issues progress will be reflected automatically in the KR.

If it's not what you're looking for, please submit a ticket and we'll get back to you shortly.

Also, here are some help articles we have on JQL:

- How do I link multiple Jira issues to OKR with JQL?

- How do I find issues linked to OKR in JQL?

Always happy to help :) 

[Dovilė Daugvilaitė-Zubcovė]

@Margo Sakova - OKR Board for Jira by Oboard  Hi! I also have the same question as Sing regarding dynamic linkage. I have projects with changing set of epics/stories/tasks throughout its lifecycle, one project usually is linked to one Key Result. How can I make sure that everything that is created on the go under project scope is reflected under KR without manually linking every new issue?

[Margo Sakova - OKR Board for Jira by Oboard]

Hi @Dovilė Daugvilaitė-Zubcovė 

The important aspect of OKRs is that you don't need to link every single task to them, only those that are actually moving the needle. Would you like me to review your current setup? I can then suggest optimizations to avoid manual work. Please reach out to me here: https://www.linkedin.com/in/margosakova/  

Regarding your specific question, we don't have the dynamic linkage you're talking about, but what you can do is link your highest-level Jira issues (epics by default) to keep track on all the sub-issues that might be added. And in case you've got a new epic - add it manually. 

Would love to learn more about your OKR strategy and setup :)