I'm sure there will be much better answers from others in the group, so I'd wait for their input. But you could certainly do what you propose below. The only downsides I can see offhand are that you have to be careful when you assign the person to a Task/Issue that you also ensure they have the correct role associated with that assignment. Then also of course you have to create two roles for each role. If you don't have many roles that's no big deal, but something to consider. We don't do it that way, but frankly I think we're weak in this area. We just tell people they're splitting their time 50% project work and 50% BAU (we call it something different but same thing). So we tell PM's that anyone that isn't 100% dedicated/assigned to the project and are also doing Scrum Team work, they should only count that person as 50% or less (and that allocation should be negotiated with the person's supervisor). And basically we manually calculate their Task Durations based on their allocation that's been assigned. It worked ok for our needs and where we are in the PM maturity model. But yeah, there's certainly a better way. Then we would check the Capacity Planning to see if any person or role is overloaded and adjust projects from there. As I said we're not great at this piece, so I'd be interested to hear what others have to say.