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

Your Points Tracker
  • 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
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?
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

Why is Resolved date/time = Created date/time for newly created Bug?

I've discoved a number of newly created Bugs on a Backlog where the Resolved date/time is identical to the Created date/time.
My assumption is that this has happened because the Report has cloned a resolved Bug and then edited the fields (I'm still investigating this).
Can anyone confirm if they've seen this issue before and if there is an easy way to clear the Resolved date/time in a case like this? I've tried to find the ResolutionDate filed in Bulk Edit, but doesn't look like this is an option.

Thanks in advance,


2 answers

0 votes
Joe Pitt Community Leader Sep 17, 2020

The resolved date/time is set when it is resolved. Is the resolved field still set or does it show unresolved?  If it is still set sending the issue through a transition that CLEARS the resolution field should also clear the date, although the date will probably still show in the history

Hi Joe, the Resolution isn't set i.e. Bug is listed in results of query including clause Resolution = Unresolved
Also, the History shows there have been no changes to the Bug since it was created, which implies the Resolution was never set.
Do you know if it is possible for someone to configure JIRA to set the Resolved date when a Bug is created? Where/how would they do this (so I can ask for it to be undone)?

BTW I've ruled out Clone of defects after speaking to individual Reporters (most of whom didn't even know of the Clone function)

Joe Pitt Community Leader Sep 18, 2020

I'm at a loss. Even if there was a script that set the resolution it should show in the history. I would open an issue with Atlassian support.

I'll try the admins of my instance first - my latest guess is that in the "Create" part of the Bug workflow it's configured to set Resolved date = Created date (goodness know why). It's not happening for all projects, so don't think it's a JIRA/Atlassian problem.

Hi Sandra

Did you find a resolution to this?

I'm having the same issue.

Just wondering if it had something to do with this?

Thanks Michael Fechter

Hi Michael,

Yes! Our JIRA Admin told me they "removed the Resolution field from the bug screen" by which I assumed they meant the Bug creation screen.

Hope that helps,

Suggest an answer

Log in or Sign up to answer

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