Excerpt |
---|
Background
At times, as a Jira user, one may want to search for Jira issues
those that are associated with UpRaise objectives as KR or with KRs as KR
actionactions. Or easily see a consolidated list of linked Jira tickets (as a KR or a KR action) through Jira’s native JQL search.
To support this feature we have introduced a new family of issue properties with the property key - UpraiseOKR. Whenever a Jira ticket is linked to an objective (as a KR) or to a KR (as a KR action), system will store relevant information of the parent objective/KR against the corresponding issue property for that Jira ticket.
You can now enable this feature on your UpRaise instance. Read Make OKR data available in JQL through issue properties. This configuration can be enabled only by UpRaise admins.
Issue properties
Below are the issue properties that are introduced under the property key - UpraiseOKR. In the table below
table, you can refer to the JQL syntax and how to use
of each property.
Info |
---|
Please notice in all the syntaxes and examples we have used issue.property[upraiseokr].<property1> AND issue.property[upraiseokr].<property2> . This means it is mandatory to the property key issue. property[upraiseokr]. |
Property | Use of the property | Syntax |
---|
linkType | This property is used to define the type of linkange Jira issue has in UpRaise, whether it is linked as KR or KR action If a issue is linked as both KR to objective A and as a KR Action to KR A, then both the values will be stored against this property
|
This property can be used along with all other properties if you wish to define Jira linkissue |
parentObjId | This property helps you retrieve Jira issues linked as KR of KRA with specified objective id If an issue is linked to multiple objectives, mulptiple IDs will be in comma-separated format
| issue.property[upraiseokr].parentObjId~<'objective id'>
issue.property[upraiseokr].parentObjId~<'objective id1, Objective id 2'>
|
parentObjTitle | Use this property when you wish retrieve issues under specific objective title If an issue is linked to multiple objectives, their titles can be stored in comma-separated format
| issue.property[upraiseokr].parentObjTitle~<'objective Title'>
issue.property[upraiseokr].parentObjTitle~<'Title1, title2'>
|
parentObjOwner | To specify name of the owner of the parent objective when the issue is linked as KR If an issue is linked to multiple objectives, their values will be stored in comma separated way
| issue.property[upraiseokr].parentObjOwner~<'owner name'>
issue.property[upraiseokr].parentObjOwner~<'name1, name2'>
|
parentKRId | Id of the parent KR when the issue is linked as KR action If an issue is linked to multiple KRs, their values will be stored in comma separated way
| issue.property[upraiseokr].parentKRId~<'KR id'>
issue.property[upraiseokr].parentKRId~<'KR id1, KR id2'>
|
parentKRTitle | To specify title of the parent KR when the issue is linked as KR action If an issue is linked to multiple KRs, their values will be stored in comma separated way
| issue.property[upraiseokr].parentKRTitle~<'KR Title'>
issue.property[upraiseokr].parentKRTitle~<'KR Title1, KR Title2'>
|
parentKROwner | To specify name of the owner of the parent KR when you want to retrieve issues is linked as KR action under specific KR owner’s KRs If an issue is linked to multiple KRs, their values will be stored in comma separated way
| issue.property[upraiseokr].parentKROwner~<'KR owner name'>
issue.property[upraiseokr].parentKROwner~<'KR owner name1,KR owner name2'>
|
objCycleTitle | To specify Objective Cycle Title in which the parent objective, parent KR, KR owner, etc might be included If an issue is linked to multiple objectives/KRs from different cycles, their values will be stored in comma separated way
| issue.property[upraiseokr].objCycleTitle~<'Obj cycle name'>
issue.property[upraiseokr].objCycleTitle~<'Obj cycle name1,KObj cycle name2'>
|
Use cases and examples
Here are some use cases and examples to show how each of the issue properties will be used in the JQL search. Please note the examples are just for your reference, you can try any JQLs as you use in Jira
day in day out. However, it is
very important to understand and properly specify UpRaise issue properties to get the required results.
Issue property | Use Cases | Sample JQL |
---|
linkType | | |
|
all the KRs | |
parentObjId | | |
| |
parentObjTitle | |
within | |
| |
parentObjOwner | | |
| |
parentKRId | | |
parentKRTitle | | |
parentKROwner | | |
objCycleTitle | | |
| |
| |
Note |
---|
Please note, this feature is not applicable for Jira issue KRs (via JQL) as clicking on the Jira issue KRs (via JQL) title from UpRaise itself will direct you to the list of issues. |