nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Sandra Atkins

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,

Sandra

Accepted answers

All comments

Joe Pitt

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

Sandra Atkins

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)?