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

Issue with fields in Jira Automation

Sharee

Hi all,

I have been wracking my brain the last few days writing automations to solve a problem (that should be a feature..) but anyway, I'm having an issue when setting the field for automation rules (in this case, the conditions rule). It shows a list of the first 50 fields, but even if I search for a field outside of that list, it doesn't typically show up.

The example attached is a simple field, due date, and for some reason it's not populating to be selected.

Can anyone help me understand this?

Thank you!

Shae - Admin to the Stars

Accepted answers

All comments

John Funk

Hi Shae - Welcome to the Atlassian Community!

You have selected Due Date already for the Field Value Changed trigger. What exactly are you trying to do with the condition?

Sharee

Hi, thanks for the reply!

This was just an example, I've had this issue when selecting other fields like target start/end as well.

But, what I'm trying to do over all is create an automation that automatically updates the dependent task's dates as the predecessor task updates theirs. (try'na make Jira a little more wagile

The condition was going to be set so Due Date was not empty.

The next step would have been a branch, so the condition may or may not be necessary? I'm not sure. but either way, the issue still is that the fields aren't populating.

Trudy P Claspill

Hello @Sharee

Welcome to the Atlassian community.

The tags on your post indicate you are using the Jira Cloud product, but the screen images you have provided are not from that product. Instead they indicate the Jira Data Center product is being used.

What version of the product are you using? Get that information by clicking the Help button and selecting the About Jira option.

Aaron Pavez _ServiceRocket_

Hi @Sharee

It seems the due date is not supported yet in the Issue fields condition.

For your use case you need to use the scheduled and a JQL as mentioned here:

https://support.atlassian.com/automation/kb/trigger-an-automation-rule-based-on-due-date-field/

Regards

John Funk

Yes, some fields like Target Start and End are not available. You would need to populate those through the Advanced setting.

But Due Date shows up for me.

Sharee

apologies, I have to use my secondary atlassian account to post on here while in the office, and it auto-tagged.

I am using Data Center

Sharee

how would you populate them through advanced settings? is that something a global admin can do, or do you mean I need a workaround?

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation

jira-automation