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?
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
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!
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