-
Suggestion
-
Resolution: Unresolved
-
2
-
27
-
Hello, Next Gen projects hit 99% of our requirements but it is absolutely critical for us to be able to add Stories to an Epic across next gen projects.
Example:
Next Gen Project A includes Epic ABC123
Next Gen Project B includes Story linked to Epic ABC123
The reason we need this is because we have shared resources across projects that need to all use the same epic. We plan our work quarterly with Epics, and members across projects contribute to the epics.
Please please enable this functionality so our company of 600+ can utilize Next Gen. Until then we are stuck with Classic.
Thank you!
Hello all,
Thank you for watching, voting, and commenting on this issue.
We use this data as well as many other inputs to feed into our prioritisation process. Linking stories to epics across team-managed projects will be something that will be available in team-managed projects, although it is not something that we will be focusing on in the next year. We want to share this with you to ensure you can plan out your use of projects within Jira Software effectively.
We apologise for the inconvenience this may cause you.
Please continue to vote and in particular please continue to add comments on how your teams find value in this feature. This contextual information of what you are doing and why you are doing is invaluable for us in providing you with a product that will grow with your needs.
Thank you,
Ivan Teong
Product Manager
- is duplicated by
-
JSWCLOUD-17778 Ability to keep the Epic Link from between two or more Next-Gen projects
- Closed
-
JSWCLOUD-22123 Add the option to select team-managed epics from other projects as parent of team-managed issues
- Closed
-
JSWCLOUD-25619 Support cross-project parenting of TMP Epics across JSW
- Closed
- mentioned in
-
Page Loading...