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

Problem with automation updating custom field

Owen Vachell

I've added a custom field called "Status updated". Then created an automation to populate that field with issue.updated whenever that field value is changed.

The trigger seems to work according to the logs but updating the field does not.

I've included a screenshot of my automation and pasted the output from the logs at the bottom. Is anyone able to see what I'm doing wrong here.

Note: I've tried using the custom field ID and the name of the field. Both give the same error.

Screenshot 2025-03-11 at 13.11.46.png

Log output:

Edited issue successfully, however some of the set fields aren't available. Fields ignored:

Status updated (customfield_10193)

Unable to find any issue field values to edit:

CW-11

Accepted answers

All comments

Walter Buggenhout

Hi @Owen Vachell and welcome to the Community!

Have you added the field to the edit issue screen for the issue type you are trying to update? Jira can only edit fields if they are on the edit screen.

Hope this helps!

Owen Vachell

Thanks for your reply. I don't see any screens that my project is using. Currently unsure if this makes a difference but this is in Jira Product Discovery. Reason I mention it is because I also can't see my custom field if I go to the main Issues settings page. Even though it's there in my JPD project. I wonder if JPD supports what I'm trying to do.

I was sure I selected a company managed project when creating this.

Bill Sheboy

Hi @Owen Vachell -- Welcome to the Atlassian Community!

Adding to the suggestions from @Walter Buggenhout ...

You note this is for a Jira Product Discovery (JPD) project. What type of field is this and where was it added?

JPD only has its "date" type field (which is a JSON representation of a range of dates), and
JPD cannot add global date / time fields currently.

And so if this a JPD "date" field, the time cannot be saved from {{issue.updated}}. A workaround would be to store the value as text and convert it to date / time when needed.

Kind regards,
Bill

Owen Vachell

Hi @Bill Sheboy and thank you.

I've been doing some digging and starting to realise this. Thank you for confirming.

My ultimate aim is to have a column that tells me how long an issue has been sitting in its current status. So, for example, if something has been sitting in its current status for 90 days, it's an indication we either need to decide it's not important enough or make an effort to decide where it fits in the roadmap.

Do you know if this is in anyway achievable. Unsure if I'm going about this the right way.

Welcome!

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

Quick Links

Find more posts tagged with

automation

jpd