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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

JQL for Roadmap fields?

Hi all!

We have an initiative field (we call it EPLC) above the epic level for use on our roadmaps and other reporting. I'm trying to create a JQL filter that will display all the epics and their children issues (tasks, bugs, enhancements, etc), but keep running into an issue with my queries, as they seem not to be available on data center?

I found this great page for cloud (Search for Advanced Roadmaps custom fields in JQL | Jira Software Cloud | Atlassian Support), but the query it suggests returns an error on data center.

Any ideas? The goal is to not have to manually update our epic list if they are tied to the parent EPLC issue.


2 answers

1 accepted

1 vote
Answer accepted

I found a workaround for anyone interested, using Scriptrunner. I built and saved a filter for my EPLC (Initiative) field, then used the saved filter to call the tasks associated with those epics.

issueFunction in issuesInEpics("filter = \"wcms eplc\" ")

0 votes
Mikael Sandberg Community Leader Dec 08, 2022

The documentation you found is only for Jira Cloud, not Data Center. Advanced roadmap in Jira Data Center is using issue links for the hierarchy instead of a custom field. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events