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
I currently have a portfolio plan, which is automatically scheduled and automatically assigns an assignee to a story (i.o.w. it's always set to Calculate).
However, when I commit the changes to push to Jira projects, the assignee doesn't get changed.
How do I force portfolio to push the assignee, as per the plan, to the Jira project?
Hi @Henk Keuris,
The team member and assignee fields do not directly map to each other as in Portfolio multiple people can be assigned to a ticket (which is not possible for the assignee field). Therefore, Portfolio will never automatically push the calculated team member in a plan to Jira.
However, when there is a single manual assignment in the team member cell in a plan, this should be pushed back to the assignee field.
So, once you are happy with the calculation of the team member for an issue, manually assign that single person to that issue in your plan, recalculate (this shouldn't affect your schedule, as it's the same person as that was just calculated), and then commit that back. You should then see that show up in Jira.
Let me know if that helps.
I hope that never isn't literal. I appreciate the limitation, but we're either requiring teams to come to Portfolio to find what they should work on or we're cutting off a powerful calculation.
I see that in the current settings you can limit the number of users who can be assigned to a story. If that is set to 1, it should then be possible to set the assignee from Portfolio. Or perhaps we could have a members field that shows up on issues?
When we're looking at larger organizations, having to manually set the assignee is not going to be a viable workaround.
Could we have a separate "Assignee" field that is just a value pulled from Portfolio? I think it would make more sense and more tightly correlate the two applications and processes if we could see who the portfolio application determined had the capacity to work on that story. Something like "Portfolio Suggested Assignee/s".
I also hope it’s something that will be reconsidered in the future. And by the way such a feature exists in SCRUM mode (bulk assign by sprint). I am currently trying to convince my colleagues to use portfolio, and there is some resistance because in KANBAN mode, there is only a manual assignation and it is far from user friendly : there is no way to preselect issues that have only one assignee suggested to auto-assign in bulk. Plus you have to scroll to find back your we resource, for each task. I would suggest adding a feature that would auto-assign a preselected bunch of issues, in bulk, the exact same way Portfolio make us do it in SCEUM mode.