I want to give each story several estimates -- one per each team that's expected to take part in its development. Here are options I considered that didn't work:
Which other options am I missing? This is essential for our ability to plan work, as our teams work on multiple projects (products) in parallel.
Is it possible to move your 'story' up a level of hierarchy to be an epic?
Then, you could have the behaviour you're after - where you can create stories per team (and assign them as you need) and have the estimate sum at the parent (epic) level.
Please let me know what you think.
I'm not sure I follow. Is 'story' a Jira story or a Portfolio story?
But regardless, I'm not sure this would work. We generally want to avoid creating stories and epics per team. We want to treat those as features (of different granularity) which can potentially be broken into sub-tasks with assignees from different teams. That's the correct representation of how our company works.
I'm in the process of trying a different solution: I found that I was wrong about skills having a fixed proportionate share, and that estimates can be set per story/epic per skill, so I'm trying to use skills as pseudo-teams.
However, I'm encountering a problem: issues with estimates for multiple skills get the error message "This issue can't be scheduled because the available team members don't have the required skill set".
At first I thought that whenever an issue has multiple skill estimates, and there's no single team with at least one member per each of those skills, it cannot be scheduled. But I found that even if I create a team with all required skills, I keep getting these errors.
A Jira story and a Portfolio story should be one and the same.
You could use skills to represent the different teams as you've mentioned.
The nuance in the error message is 'available' team members.
Do you have any team members with upcoming availability constraints? (For example, have you set up any future holidays, team specific availability?) Is there any limit which could be preventing one of your team members with the skill from being scheduled to work on your epic?
You also don't need to have all the available skills in a single team - this can exist so long as someone in your plan has the relevant skill.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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