You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I can export all issues including exports, but can't get the field that has the epic that the issue belongs to. I can do this for Jira, just not next-gen.
Hello Kristin,
Welcome to Atlassian Community!
Next-gen Epics does not have the same fields as classic projects, so there are no fields which relate a next-gen Epic to its "Child" issue. This is was an intended behavior when developing this new template to keep the proposal as simple as planned, however, we see now that it is causing some lacks in the export and JQL search functionalities.
That been said, we have created a feature request to change this setting:
- As a user, I'd like to be able to use JQL for Epic Link for Next-Gen project epics
Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.
For now, we recommend you to use a custom text field to manually add the Epic reference to the issues.
Let me know if this information helps.
For those looking, this now works with the parent field. https://jira.atlassian.com/browse/JSWCLOUD-17239
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.