We have an agency that wants to manage several portfolios and they want to create releases for each portfolio. However each portfolio will be creating releases at the same time and using the same epics. I don't believe the agency needs to be using releases when it appears their goal can be to use a Theme> Initiative>Epic hierarchy to create a roadmap which is what they really want and I am concerned that if they create a release at the same time we have one and map the same epics into their release also, this will create problems for tracking, reporting and delivery.
Welcome feedback/thoughts/recommended approaches.
I would tend to agree with your line of thinking. As much as that maybe be what they have asked for I don't believe it will yield the results they are looking for from a reporting stand point.
That being said, from a technical stand-point there is nothing preventing them from adding the same epic issue type to multiple versions as from a different use case where the epic is your top level you might want to have it tracking over multiple release where you are continuing to complete stories until the epic is considered complete.
Based on what you have described I think your line of thinking for configuration makes more sense.
Just my two cents.
-Jimmy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.