Automation Rule fails due to status being a non editable status

[Jeffrey Bistrong]

I have an automation rule that is failing due to the ticket not being editable. Trying to figure out how I can add an exception to this status properties that would allow the automation rule to make the edits it needs to

[Thomas Schlegel]

Hi,

you can get all issues changed by a user with this JQL: 

project in (PROJECT) AND status changed from "Open" to ("Resolved", "Closed") during("2013-10-01", "2013-10-17") by <username>

But you can't get the number of times, the issue moved between dev and test. For this, you need a customfield that increments every time, you'll reach the test-status.

[Виталий Князев]

Thank you for the reply, Thomas!

Does this JQL work in follow case:

Let's take simple workflow To Do --> In Work --> Test --> Closed

Bob (developer) get Issue in Work status at 1 of May 2018. During development he ask Mike (developer) to help his with issue, so Assignee user changed to Mike at 2 of May 2018. 
Finnaly, Mike done issue and move to Test status at 03 of May 2018.
Ann in position of tester, start to test issue and assign it to her.  Later move it back to In Work status on Mike at 04 of May.

So, I start to run JQL at 05 of May 2018.

project in (PROJECT) AND status changed from "Test" to ("In Work") during("2018-3-1", "2018-3-4") by Mike

and 

project in (PROJECT) AND status changed from "Test" to ("In Work") during("2018-3-1", "2018-3-4") by Bob

will return the same issue in both JQL?
I meen Assignee User field have different values during the time, JQL search only by the value at runtime?