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; } } }

Can I query the change log without a change trigger?

Dancey Apple

I'm trying to pull the previous value of a custom field that has already changed using automation. This is on Data Center.

Does this only work when the rule is triggered by a change?

I'm using {{#changelog.[fieldname]}}{{fromString}} to {{toString}}{{/}} to try and search based on automation documentation, but I'm not getting any results.

Accepted answers

Mohamed Benziane

Hi,

It seems that you can only access to the smart value "field change" using an update trigger.

One solution could be to use the REST API in Automation

All comments

Mohamed Benziane

Hi,

It seems that you can only access to the smart value "field change" using an update trigger.

One solution could be to use the REST API in Automation

Bill Sheboy

Hi @Dancey Apple -- Welcome to the Atlassian Community!

Adding to the suggestions from @Mohamed Benziane ...

If you try using the REST API endpoint to get the changelog, you could run into the limits for how many entries are returned for each call. And so if your issue is updated often and the assignee changed more than 100 "changes" ago, your rule would be quite complicated.

What problem are you trying to solve by doing this? That is, "why do this?" Knowing that may help the community to offer other solution approaches.

Kind regards,
Bill

Dancey Apple

Hey @Bill Sheboy and @Mohamed Benziane Thanks for the suggestions!

The goal is to plug the old value of the field into a new field.

We have a field called Remaining Hours that was zeroed out by another automation. We want to grab the previous value and plug it into a new field called Estimated Hours.

Bill Sheboy

Is this a one-time fix or a re-occurring one?

one-time fix
- I recommend reviewing the issue change log / history and updating the field manually
re-occurring fix
- First thing, review the other automation rules to prevent them from clearing the field
- As I noted earlier, when the field was cleared is important, as the REST API cannot return all the change history to find the field clearing. If the clearing happened within the last 100 issue updates, a single call to the REST API should reveal the prior value. If not, the rule changes are much more complex, as it is likely a recursive rule with an Incoming Webhook trigger will be needed to solve this.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-data-center

automation

data-center

smartvalues

changelog