Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,529
Community Members
 
Community Events
184
Community Groups

Original Estimate

Hello Community,

Here is my question...

My cards on the board have single assignee. an original estimate value is entered to each card. I've added a custom field - multipe users so i can include other people of also work on that card.

 

The problem - How can i record the effort of these multiple users? is there a way the original estimate will be applied for these users as well as the assignee?

 

Thanks,

Amir

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 12, 2023

Welcome to the Atlassian Community!

The original estimate is intended to capture all effort on the issue, but it has nothing to say about who has to complete all the work!

The assignee is the person working on, or at least the single person currently responsible for, getting the issue done.  You don't want multiple assignees at the same time, that really fails hard in real life, but you can have many over time.  That's why the assignee can be changed!

Imagine this lifecycle:

  • Alice the product owner creates an issue, with an estimate of 4h
  • Bob the developer sees it
    • Assigns it to himself
    • Does some work on it
    • Logs 2h on it
    • Assigns it to
  • Charlie the tester
    • Tests it
    • Marks it pass or failed testing
    • Logs 1h work on it

Result - original estimate 4h, remaining estimate 1h, logged work 3h, Bob and Charlie have separate work logs on their timesheets.

That's a highly structured process, and I left out the workflow there to keep it simple (new -> dev -> test -> done) 

You will often find less structured cases where Bob asks Dave for help with the coding.  They won't reassign the issue (it's still Bob's job to get it done), but Bob and Dave will both log work on in - you don't have to be the assignee to record effort!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events