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

JPD How to create an automation to set "Target Quarter" from work item due date?

André Ribeiro_3iiii9

Hi,

I'm using Jira Product Discovery with a Team managed project.

I have 2 project specific fields:

Date field "Due Date" e.g. 2026-11-30
Short text field "Target Quarter" e.g. "2026 Q4"

I'm trying to use automation to set the "Target Quarter" from the "Due Date" by setting the formula to

{{issue.duedate.format("YYYY")}} Q{{#=}}{{issue.duedate.month}}/3{{/=}}.ceil

but it always returns the following error (cf image below):

Edited work item successfully, however some of the set fields aren't available.
Fields ignored: Target Quarter (customfield_10487)

The rule is configured in the following way:

Can anyone help?

Thanks,

Accepted answers

ManuA

Hi @André Ribeiro I'm from the JPD Team. I'm assuming here that the target field, ie "Target Quarter" is in JPD.

Since it's a short text field, ideally JPD date formatting shouldn't be an issue. Having said that, could you try switching the actor of your automation from "Automation for Jira" user to another user (perhaps your own user account that would have access to JPD). In certain cases, we have noticed "Automation for Jira" user not being able to interact with JPD automations.

Based on the results, please feel free to open up a support case here: https://support.atlassian.com/

If it is the A4J user issue, then we will need to get that fixed from the backend, and if that is not the root cause, we will need to look into this further

Also, I cross checked the expression you shared and unfortunately this did not work for me:

{{issue.duedate.format("YYYY")}} Q{{#=}}{{issue.duedate.month}}/3{{/=}}.ceil

Perhaps it was truncated?

I wrote a slightly different one to pull the due date off an idea and paste it with the format "YYYY QQ"

{{issue.duedate.format("YYYY")}} Q{{#=}}CEILING({{issue.duedate.format("M")}}/3){{/}}

Also, you can always add a "Log Action" action before the edit, and it should see if the right value/format is retrieved/made.

All comments

Bill Sheboy

Hi @André Ribeiro -- Welcome to the Atlassian Community!

First thing, let's confirm what / where you are trying to update the fields...You note both a JPD project and a Team-managed project (TMP). And you note "Due Date", which is a built-in field.

In which project are you trying to update the "Target Quarter"?
What type of field is "Target Quarter": a global date / time field, a TMP date field, a JPD date field, text, or something else?
When you use "quarters" and "years" are they based on the calendar year or the week-of-year?

Until we know those answers...

Based on the audit log error, the field "Target Quarter" field is not available for the project (or views) of the field you are trying to update. Knowing where the field is will help narrow this down.

If the field is a JPD date field, that has a different format: a date range of JSON represented as text. Thus, to set the quarter is different than the method you show.

Finally, when formatting dates, the "YYYY" format is the week-based year and "yyyy" is the calendar-based one. At the year boundaries the values are different. For example, for 29 December 2025 in the Due Date:

{{issue.duedate.format("YYYY")}} will be 2026

and

{{issue.duedate.format("yyyy")}} will be 2025

Kind regards,
Bill

ManuA

Hi @André Ribeiro I'm from the JPD Team. I'm assuming here that the target field, ie "Target Quarter" is in JPD.

Based on the results, please feel free to open up a support case here: https://support.atlassian.com/

If it is the A4J user issue, then we will need to get that fixed from the backend, and if that is not the root cause, we will need to look into this further

Also, I cross checked the expression you shared and unfortunately this did not work for me:

{{issue.duedate.format("YYYY")}} Q{{#=}}{{issue.duedate.month}}/3{{/=}}.ceil

Perhaps it was truncated?

I wrote a slightly different one to pull the due date off an idea and paste it with the format "YYYY QQ"

{{issue.duedate.format("YYYY")}} Q{{#=}}CEILING({{issue.duedate.format("M")}}/3){{/}}

Also, you can always add a "Log Action" action before the edit, and it should see if the right value/format is retrieved/made.

Bill Sheboy

Hi @ManuA

Please see my post regarding the differences between the format "YYYY" and "yyyy". It is likely many customers use calendar-based years rather than week-based ones.

And, for @Hermance NDounga -- I respectfully suggest not accepting a solution on behalf of the people asking questions when they have recently asked it. Instead, please allow the original poster to decide and accept. Thank you!

Kind regards,
Bill

Welcome!

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

Quick Links

Find more posts tagged with

custom-field

automation

team-managed-projects

jpd