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.
Adding a member is not a good solution because when later I run a search with that person name, it will return me tasks in which that person is ALSO a member but not necessarily the person in charge.
It’s quite strange that a PM tool like TRELLO does have this basic function…..
Hi @Dante Welcome to the community! Typically the member field is used as the way to communicate who's assigned to the card, but some people add themselves as members if they are a collaborator or want to be notified of the card.
I'd suggest making it a standard rule that members should only be used as the assignee, and there should only be one member per card. If someone is a collaborator, then a checklist item within that card can be assigned to them, or if they're just wanting to follow the card, they can simply watch the card to be notified of changes.
An alternative would be to use a separate field to clarify the main owner or person responsible like a dropdown custom field or a label (see Roxanne's post).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.