Why is Resolved Date only set using a Post Function?

[ChristopherChilds]

Hi All,

I am confused why it is that a "Resolved" Date can only be created when a user adds a post function but can NOT be added when a user manually sets a resolution. For me, I feel that this should be an option available to all.

[John Funk · Accepted solution]

Hi Christopher,

I assume that the thought is that setting it manually would simply be updating the field verses an actual action by the system. For example, you could set the value of the field at any point in the process - meaning that just because the field changes doesn't necessarily mean that it is completed. Anyway, not sure why Atlassian did it the way they have done it.

[ChristopherChilds]

Hi John,

Many thanks for your answer. I would first like to apologies, the field in question is actually "Resolved" and is a date time field.

This field only appear when using the post function to set a value of the "Resolution". This field does NOT appear when setting the resolution manually in the UI. 

This field is not listed under System Fields or Custom Fields in the Jira Administration area.  This field is also not available in Field configurations and as part of Project Automation.

Do you think this could be a strange bug?

I am on 8.20.11

[John Funk]

I think the Resolved field is like the Created field. You have no control over it all - it gets timestamped when a certain event happens. So, in this case, it's probably stilled tied to what I mentioned above - it only fires when the Resolution is set in a programmatic way, not just a field update. But that's mostly just an educated guess as I don't know for sure.