Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Auto Assigning doesn't Reference Most Recent Change for Some Reason

Chris Barrett
March 10, 2022

Hello! Sorry this is a little long.... but I have been trying to find a way to auto-assign a "Fix Failed bug back to a developer that attempted the fix and I found a decent solution. However, I am still running into a problem that I can't figure out.  

What I am doing is this: I have a custom field called "Fixed By" that automatically populates the name of the Dev who entered a value in the "Fixed in CL" field.  I then added a Post-Function to update the Assignee based on the value of the "Fixed By" field. (Fixed by "Dan" = Assigned to "Dan", for example) This works swimmingly for the most part, except for one thing... 

Here are the steps that lead to the problem:

  1. Bug is assigned to Dev 1, and Dev 1 makes a fix attempt.  The bug auto-assigns to QA for regression. 
  2. QA Fix Fails the issue and it automatically returns to Dev 1 (per my automation described above -- this works perfectly). 
  3. Dev 1 is too busy with other things to make a second fix attempt, so they pass the bug to Dev 2. 
  4. Dev 2 makes a fix, sends to QA for regression and the "Fixed By" field automatically updates to Dev 2 as it should. 
  5. QA Fix Fails the bug again (it happens sometimes lol), and for some reason the bug automatically assigns to Dev 1. 

In this case I want the bug to go back to Dev 2, but for some reason Jira ignores the fact that the Fixed in CL field was more recently updated by a different person the second time around. I don't know if there is a solution to this... it almost feels like an unintended bug to me.  Any thoughts or suggestions would be greatly appreciated. Thanks! 

 

1 answer

1 accepted

0 votes
Answer accepted
Ste Wright
Community Champion
March 26, 2022

Hi @Chris Barrett 

Can I confirm if this is Cloud or Server/DC?

And what Automation functionality are you using for this? Is it native Automation?

Ste

Chris Barrett
March 28, 2022

@Stephen Wright _Elabor8_ This magically started working for me without me having to change anything. Not sure what happened but I'll take it. 

Jira is now working as I expect it to. Here is what it is doing, just in case anyone else finds this and is interested. 

When the bug is marked "Fixed" by a Dev they are required fill out a "Fixed in CL" field, and a custom field called "Fixed By" automatically populates with the person that changed the Fixed in CL field.  The bug then transitions automatically to Test for regression using a "reassign to reporter" automation.  QA  performs regressions, and the bug fails and needs to go back to Dev.  At this point I use a Post Function that checks the "Fixed By" field and automatically assigns back to that person when the bug transitions to Fix Failed. 

Like Ste Wright likes this
Ste Wright
Community Champion
March 28, 2022

Glad to hear this fixed itself :)

Ste

Like Chris Barrett likes this

Suggest an answer

Log in or Sign up to answer