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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Assign the task/ticket back to the reporter. I didn't understand what's the concept here ?

Are we able to track if we complete the task and then just assign it back to the reporter. 

Didnt get the flow. 

Please help.

2 answers

1 vote

Some places find it useful - after all, the assignee is the one person currently responsible for dealing with the issue, and it makes sense to say "you reported it, it got fixed, so it's yours again now".

But it's just as valid not to bother - the assignee field will then contain "the person who was last responsible for dealing with it."

0 votes
Dave Mathijs Community Leader May 18, 2022

Hi @shreyas sinha Nanu  Welcome to the Atlassian Community!

There's no need to assign the task to the reporter when it's completed.

The Reporter is the requester of the task (as I see it), the Assignee is the one who executes the task.

Assign ticket back to the reporter for verification that the issue was resolved to their satisfaction.  Once reporter verifies the ticket status goes to "verified" and can be "closed" at the next change control board (CAB) meeting.

Suggest an answer

Log in or Sign up to answer