Can I link new issue to non-Epic from Requirements blueprint?

Hi.

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?

Thanks.

Regards,

Luis

0 comments

Comment

Log in or Join to comment
Community showcase
Bridget Sauer
Published Jan 29, 2018 in Confluence

Showcase: How LinkedIn does Content Lifecycle Management (12 Steps)

LinkedIn, the world's largest business network has an exceptionally large Confluence instance. In their case, large means millions of pages and thousands of spaces. In this Showcase, we're focusing i...

509 views 0 8
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot