Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Status no longer works in searches using "changed to" Edited

I used to be able to run a search with the following and get good results.

project = smart and status changed to Done during (-70d, 0d)

Now the above search returns zero results in spite of the search below returning many results, all well within the expected timeframe:

project = smart and status = done

I have three projects in my Jira cloud account. If I remove the project from the top query, I get a lot of results but only for one of the projects. All of the projects have a state called "Done". What could be causing this?

 

edit: I did recently change the ordering of statuses in /secure/admin/ViewStatuses.jspa. Is it possible Jira has lost all the history for status changes because of that? 

2 answers

1 accepted

2 votes
Answer accepted

Hi @Daniel Covill 

My understanding is that symptom can happen when you use any Team-managed (formerly called Next-Gen) projects in you instance.  Are you doing so?

If so, the cause appears to be each project has it's own version of each status, and so CHANGED, WAS, etc. get confused.  The work-around is to use the specific status ID value.

project = myProject AND status CHANGED TO 12345 DURING (-70d, 0d)

Your site admin should be able to determine the specific status ID for you.

 

Best regards,

Bill

This was the answer. 

Like # people like this

Here are the two defects for this symptom.  You can watch them and/or mark that they impact your team.

Like # people like this
Like Bill Sheboy likes this

Hi @Daniel Covill ,

You JQL looks good and reorder statuses should be a reason to lost history of status change, this information is stored in the issue changelog.

I would recommend you to open a ticket to Atlassian support because this might be some issue in your instance and they will be able to provide you the troubleshooting steps.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you