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
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've created a page from the Requirements Blueprint and in the "page properties" table, I filled in the "Epic" field with an issue key that doesn't correspond to an Epic (custom issue type).
I was expecting that, once I created a new issue from text selected in this page, it would propose me to link it to the issue in the "Epic" field, not only if the issue is of type Epic.
I can't seem to find a way of modifying this behaviour. Is there a way to do it without having to later on do some batch editing in JIRA?
In our JIRA project, we try to reserve Epics for "stories that cannot be implemented in one sprint" (JIRA is for developers). Requirements should be linked to a business project represented by an "XYZ Project" issue type (Being XYZ the type of the project managed in the PM tool). We don't use JIRA for PM stuff or have Portfolio or other add-on. Btw, anyone knows if having Atlassian Portfolio would allow to have a requirements page linked to a Program or Feature?