When the System Fields (such as Due Date) are updated?

[Luiz Bitt]

Does anybody know when the system fields are updated (for example, on the creation, in the transition, etc.) ? Is there a table describing when each one are updated?

[Nic Brough -Adaptavist-]

They are updated when the user changes them.  They might do it with an edit, or during a transition, or by triggering an automation or script, etc, and they could be changing almost any field in any of these.  Most of the options come back to how you have configured your Jira workflows and automations and listeners if you have any.

The main exception to that is the "updated" date/time - that is calculated by stamping "now" into it on any change made, rather than letting the user change it directly.

[Luiz Bitt]

Hi Nic, thanks for your explanation and that's what I thought!

Some fields are just simple to identify an update (eg. Sprint Start Date), but others such as DUE DATE aren't easy. Even when I transition the Issue from a column to another, this field (in particular) is not updated.

So, I wondering if that's some table (or page) explaining when each system field is updated (by default, in an out-of-box installation). It doesn't matter if it's in an edit action or in a transition, I just want to know what fires the update and when.

Glad if you have some info or know where I can find it!

Tks!

[Nic Brough -Adaptavist-]

Again - fields are updated when the user changes them.  I'm stuck on what you don't understand about that.

[Luiz Bitt]

Hi Nic, I apologize for not being clear...

What I mean is that I'd like to know which system fields are automatically populated (by some internal process/scripts) and which one are filled by the user itself.

For example, I know Sprint Start Date is automatically populated when issue is transitioned to an existing Sprint, but how about Due Date, Actual Start Date, and Actual End Date? Are they filled manually or automatically?

Thank you!

:)

[Nic Brough -Adaptavist-]

Actually, sprint start date is not set quite automatically.  It is entered by the user when they create or start the sprint, and then read from the sprint when needed.

The only fields the system fills directly are creator, created date and updated date.  Everything else is entered by users, or derived from combinations of data that has been entered by users.

[Luiz Bitt]

Got it!

Tks for your help (and patience)!