Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,555,228
Community Members
 
Community Events
184
Community Groups

Identify all delivery tickets linked to a specific Idea

Edited

Hey there, is there a way to identify all delivery tickets that are linked to an idea, ideally through a field or JQL?

For context: Our current hour reporting is based on epics (using a 3rd party application). Reporting by epics is easy because in Jira we can group tickets by 'Epic Name', which allows us to roll up the hours spent on all tickets that are linked to a specific epic. 

As we're considering rolling out JPD to our teams, we want to be able to roll up the hours spent on all tickets that are linked to a specific idea. Is there a specific field we could use for that? 

 

 

1 answer

1 accepted

2 votes
Answer accepted
Jan-Hendrik Spieth
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 28, 2023 • edited

Yes, you can search for linked issues using the linkedIssues() function. The only catch is with the type of the link, because it seems the polaris link type "implements" cannot yet be used as a filter.

So for example:

issue in linkedIssues("IDEA-123")

This will return all issues that are linked to the idea, not only the delivery tickets. But maybe that still helps, already?

Thanks @Jan-Hendrik Spieth

This is helpful! The issue we have with this approach is that only tickets that are 'directly' linked to the idea show up as 'linked issues'. For example, if I link an epic to an idea, only the epic itself shows up as 'linked issue'. The child tickets that are linked to the epic however don't show up as linked to the idea. 

Like Jan-Hendrik Spieth likes this

@Mirko Grahnert You can use the above suggestion to get the directly linked issues and linkedIssue in linkedIssues("IDEA-414") to get the linked issues and also the sub-tasks of those linked issues. This will return what you need.

Like # people like this
Like Jan-Hendrik Spieth likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events