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
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,
Sandra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sandra,
Can confirm this fixed our problem too - removing the 'Resolution' field from the projects screen(s).
Thanks for letting us know.
Regards Michael Fechter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
BTW I've ruled out Clone of defects after speaking to individual Reporters (most of whom didn't even know of the Clone function)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.