that's exactly the right way to go - the reason for this being configurable is that in many teams, multiple people work on a story, and the issue assignee is just the "owner" or main responsible person. If you have a 1:1 mapping between assignee and the person doing the work, then changing the assignee import level does the job. side note: Release 1.12.6 recently added that when changing the assignee in Portfolio, in case it is a single person, gets commited to the issue assignee in JIRA too (there's a setting to turn this on/off as well)
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