In foresight, I feel that would be depending on the nomenclature your use. A typical segregation could be Product A which may have Portfolio Epic - 1, 2, 3 and so on. However, there is nothing stopping you from identifying a Portfolio Epic based on your requirement. Note that JIRA may recommend the typical way mentioned above.
I have 10 Portfolios. Each portfolio is dedicated to unique set of products/services. I create a portfolio epic (initiative) that extends the value of 1 or more of the associated products. I would like to associate those specific products impacted to that portfolio epic. It seems there are conventions for defining Products in the tool- I can't find and more information on this however. I don't think using tags is appropriate.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One way could be to evaluate at creating a Parent Product Portfolio Epic (use some agreed naming convention & distinct for each product) --> Tag your existing Portfolio Epics --> Features (Epics) --> User Story ....and so on.
This could be a "hack". There could be other possibilities for executing this better.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.