How to get all Tickets in Advanced Roadmaps to show

[Heather Ronnebeck]

Currently, I am working on a problem where I can only get some of the tickets to show up under the epics in my Advanced Roadmaps. I have a feeling the problem is in my Scriptrunner JQL I'm using. 

Basically I have one epic that has over 100 tickets in it, but only 1 of those tickets shows up on my roadmap. 

My scriptrunner JQL is:

issueFunction in linkedIssuesOfRecursiveLimited(issuekey="ABC-130", 3) and project != ABC

All of the projects being called in are company managed, and not in the ABC project as expected. I'm wondering how I can get more in. 

The structure here is:

ABC Project standard task 

(Using issue linking) -> DEF Project Epic

(Using Epic to Story linking) ----> Story/Bug tickets

If anyone has any suggestions I'd greatly appreciate any help I can get here.  

Thank you!

[Tom Lister · Accepted solution]

Hi @Heather Ronnebeck 

If your JQL returns all the tickets you expect, then click the Filter dropdown on the roadmap and check for any further selections.

[Heather Ronnebeck]

I don't think it is though, @Tom Lister . I think I am missing tickets in my filter because I'm only getting back 270 ish tickets and there are a LOT more than that. 

[Tom Lister]

Do you have the function 

linkedIssuesOfAllRecursiveLimited

available on your system. I think it might have been deprecated but it behaves differently re Epics

[Heather Ronnebeck]

It's in the cloud and I thought I did have it enabled. It lets me use it. I wonder where I can go to check that. 

[Tom Lister]

Did this function help at all?

[Heather Ronnebeck]

I'm using that function in my JQL already. It isn't pulling in any more tickets than before. Is there another spot I could look or try?

[Heather Ronnebeck]

I expanded the levels on the function and it still won't acknowledge the stories inside epics on the Advanced Roadmaps View. It only goes as far as epics. 

[Jamie Edmondson]

Hi @Heather Ronnebeck , couple of questions:

1. Is your filter selection in Advanced Roadmaps allowing everything below an Epic to be viewed? For example: Hierarchy that's in view includes Feature - Sub-task? I am assuming it does, but thought I should ask.

2. Would it be possible to add a label to all of the issues and build your filter around that instead? I've also struggled with "linkedIssuesOfAllRecursiveLimited" and I gave up on it and went down another path.

-Jamie

[Heather Ronnebeck]

Hi @Jamie Edmondson 

From what I'm seeing it looks like there are no filters at all on the roadmap. Everything's in there showing as All issue types. 

I just noticed I can add more than one source for issues. Maybe I can try that route to get more of the tickets in. Just have to build the queries right I think. 

[Heather Ronnebeck]

@Jamie Edmondson @Tom Lister 

Just to come full circle on this, for others that are looking for answers. 

The problem was that I was trying to use one JQL to do this, when in fact I needed two or more filters. I created a second and third filter to grab the other tickets and just added them as multiple sources in the Plan Issue Sources configuration. 

Thank you for all of your help!

[Jamie Edmondson]

@Heather Ronnebeck , yes and that makes sense. You can add an entire board or project to the roadmap. Then you can remove any tickets that would not belong in the plan by using the Bulk Actions button. Removing issues will not impact the issues in any way, it just removes them from your plan-view.

[Tom Lister · Accepted solution]

Hi 

Just a quick follow up and an alternate solution.

I used this query to get all Epics linked to an Initiative in our Roadmaps

issueFunction in linkedIssuesOfRecursive("issuekey=CLOUD-47")

This was then saved as CloudInitiatives.

The I set up a query to get the children of Epics using issuesInEpics . The source JQL for the Epics is the previous saved filter i.e.

 issueFunction in issuesInEpics(" filter = CloudInitiative")

 The results can be combined to give epics and children with a simple or 

filter = CloudInitiative or issueFunction in issuesInEpics(" filter = CloudInitiative")

I hope that helps.

Tom

[Heather Ronnebeck]

That also helps a lot. Thank you.

[Tom Lister]

I think function traverses issue links. The Epic/Story relationship is held differently. I thought the ‘All’ function got around that. There is a way to join two sets of filter results but I need to search for that