Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Resolved date changing when Resolution changes from an existing value. Is that correct?

Justin Hayes
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 8, 2018

I'm aware that Resolved date is set when the Resolution field itself is set. This makes sense, though I wish it wasn't so tightly coupled.

However it also seems to change date if you change the value of Resolution once it's already set. We have a review step once an issue is resolved and on that transition we might change the Resolution in order to correct it. I wouldn't expect that change to alter the Resolved date though.

Is this a bug? Is there some way to put the original date back?

Thanks!

Justin

1 answer

0 votes
Joe Pitt
Community Champion
June 8, 2018

It isn't  a bug. It is working the way it is designed. A 'bug' is a deviation from design or requirement. You just don't like the design. I would want the date updated when the resolution changes. The history will have the old date.

A work around would be to set a custom field 'Original Resolved Date' with a post function to the date when the resolution is set. Then have a transition to change the resolution that doesn't have the post function. 

Justin Hayes
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 8, 2018

Thanks. I understand the definition of a bug and not having access to Atlassian's design docs means I can't easily say if it is or isn't one :) Unless this exact behaviour is documented for us?

Personally I'd say changing the date in this case was wrong - an issue is resolved when Resolution was set, not when Resolution changes without reopening. I'm not talking about issues that have been reopened and then resolved again.

I'd also argue that the setting of the Resolution date shouldn't be bound to setting that field at all and it should be possible to set it based on workflow state transitions, but that IS a design decision :)

Like Kim Kassmeyer likes this
Hani Juha August 27, 2018

Something seems to have changed.  I don't remember the Resolution Date changing when Resolution changes from some value to another value.  I have a script running against jira that is looking at the Resolved date.  Now, all the metrics are off.  as the Resolved date is being updated when the resolution is being updated.

 

What is the JIra definition of resolved?

 

I thought it was Resolution changing from <null> to a value?

Suggest an answer

Log in or Sign up to answer