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

approvals in assignee change in JIRA.


My Use case as follows.

I have Task (or sub task) in JIRA project.  when i assign my Task to another JIRA user, assignment was success .

Currently Task is assigned to person 'X' and Person X assigned this task to 'Y', assignment attempted and it is success , now the task is assigned to 'Y'.

but I'm looking different approach/scenario.

in my use case, when Person X assigned task to Y, it should Request approval (yes or no) from Y, If Y approves (i.e. Yes from Person Y) the Task gets assigned in the name of Y else it must be in the name X. 

till Y acknowledges (Yes or no), the Task must be in X name only. 

Any solution(s), pls comment.

1 comment

Suhas P
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 09, 2021

I think you are complicating the process. It is advisable to keep the process simple as it will have low maintenance in the future. In your use case, why can't the current assignee (X) just comment on the issue by mentioning the person (Y), then person Y can assign the task to himself.

Or you could have an additional transition (button) (Person X transition the task) like Waiting for Team A (Example, Waiting for Testing), and then another team/person will pick the task from there. Additionally, you can send an email to the team/person when the task is in that status.

on the lighter note, I do accept that making the process complicated. But here are my comments.

our team connected remotely and from (i.e. Geo-graphically) all over the Globe. The tasks were lined up (as per project) and we are looking for Tailored process though it is complicated, ( im even looking better than this ) but intend to  help Project monitoring/ Live tacking. 

1. initially applied data from comment section, but not helping anyways. i.e. Ground reality is different.

2. The other idea Waiting for Team A is something on Work flow based.  it is in-place. my use case was different .


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events