You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Currently I am working within a JIRA instance that has many projects with many versions (think of a lot of minor versions like "1.0.1", "1.0.2", "1.1.0", "1.1.1" etc). This is resulting in a Portfolio timeline filled with circles of release start and end dates.
Any advise that somebody can give me to deal with this?
Hi Wessel! How are you doing?
Are all of these versions related to projects, that really need a plan, or some of them are small fixes that your team does in a few hours?
I would leave in Portfolio only the releases that are related to projects and would remove from the plan the other ones.
Hope this helps!
That actually helps a lot.
It also becomes clear to me that Portfolio for Jira isn't a tool that can magically create timelines from tickets that have no planning whatsoever.
That being said:
How would you use Portfolio in an environment where no versions are used at all. One of my clients is doing so many releases that creating versions is not doable.
As you progress in time stories become more vague without estimations. That part is clear: but what about Epics and Initiatives? Looking at Teams In Space they all look nice in the time-line.