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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
Looking to learn more about best practices for when it comes to assigning tasks and being aware of what's in someones court.
Currently if I look at my personal board for open issues I have some tasks that are there but there are lots of other efforts that I'm leading in a sense that don't show up in this board since I'm not the assignee. What's typical for someone to do? Assign the epic to the owner of the epic and from there the epic will always be in this filter?
The end goal is that we have an accurate representation of what's in someones court and even though a component is assigned to someone else the task as a whole is still owned by me.
Thoughts on best practices? How does everyone else deal with this?
I'm just in the internal systems department, we don't have sprints either. For me it's just a matter of how to organize tasks that I run but aren't in my court. Perhaps assigning the epic to myself and the sub tasks to others is the way to do it?