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

Automation rule question add x weeks to a date

Felix Köhn

Dear all,

I'm trying to create an automation that sets a due date with a given start date and a duration.

When value changed for start date:

create smart value based on duration X
edit due date
- {{issue.customfield_<ID>.plusWeeks(<Smart_Value_X>))}

It gives an error "Failed to get value for..."

The customfield-ID is the ID of the start date.

If I set the duration field to 4 it shows that the Smart Value X is 4 in the automation log.

If I change the <Smart_Value_X> to a hard coded 4 in the automation it works aswell.

I cant get him to use the smart value in this operation.

I tried with a free text field and a number field for duration.

Start and due date are date fields.

Do you have a Suggestion?

Accepted answers

All comments

Florian Bonniec

Hi @Felix Köhn

Why do you need to use a variable ? Could you not use

Regards

Felix Köhn

Hi @Florian Bonniec

because the duration is variable (not always 4) that can also change at a later date.

If I create a work Package and i know the start date but not the end date, I can freely play around with the duration / start date and have it adjust automatically.

Florian Bonniec

Can you share the automation configuration ?

Felix Köhn

When: Value changes for

Start date / Duration
Create Issue; Edit Issue

Then: Create Variable

Variable Name: Duration
Smart Value {{issue.customfield_XXXXX}}

And: Edit Issue Fields

{{issue.customfield_XXXXX.plusWeeks(Duration)}}

The Edit Issue Field is the End date

Unfortunately I cannot upload Screenshots.

I'd expect End date = start date + duration
But the End date is empty

Cristian0791

Hi Felix,

Hope you are doing well.

On the last step

{{issue.customfield_XXXXX.plusWeeks(Duration)}}

try to use (Duration.asNumber) instead of (Duration)

Felix Köhn

Hey Cristian,

thank you for the suggestion.

with {{issue.customfield_XXXXX.plusWeeks(Duration.asNumber)}} the field is still empty unfortunately.

I also did
And: Add value to the audit log

and added the "End date" issue.customfield to see if it has any content.

The field shows to be empty in the Automation Audit Log too.

Cristian0791

Hi Felix,

You can try the following.

Provide a value mannualy to Start date and see if the End Date is edited after.

Maybe is a problem beacuse Start date is empty.

Cristian0791

Also please make sure that:

When: Value changes for

Start date / Duration
Create Issue; Edit Issue

Then: Create Variable

Variable Name: Duration
Smart Value {{issue.customfield_XXXXX}} Here you have the customfield id for Duration

And: Edit Issue Fields

{{issue.customfield_XXXXX.plusWeeks(Duration)}} Here you have the custom field id for Start Date + variable

Bill Sheboy

Hi @Felix Köhn

There is an intermittent defect for this symptom for Jira Cloud, where variables cannot be consistently used to increment date / time values...even when converted with asNumber.

I do not know if this defect also applies for Server / Data Center automation, but you could try two workarounds:

{{issue.customfield_12345.plusWeeks(varMyVariable.asNumber)}}

or

{{#issue.customfield_12345}}func=plusWeeks({{varMyVariable}}){{/}}

Assuming customfield_12345 is a date (or date / time) field and varMyVariable can convert to a number, both of these currently work for Jira Cloud.

Kind regards,
Bill

Felix Köhn

hey @Bill Sheboy

thank you for your suggestion.

Unfortunately both options do not work in Data Center.
In both cases the field is still empty.

This is definitely a Bug in the Software.

Felix Köhn

Hi @Stefan Salzl

I saw your working suggestions in different posts and was wondering, if you have an idea or solution for this problem.

Kind Regards

Bill Sheboy

Thanks for confirming that. At this point, I would work with your Jira Site Admin to submit this as a defect at the link below. The earlier defect I noted is for Jira Cloud, and it will be good to let Atlassian know the scope of this problem.

https://support.atlassian.com/contact/#/

Stefan Salzl

Hi @Felix Köhn

Obviously the bug that variables can´t be used in calculation occurs in DC too.

If there is no urgent need to solve this via variable (as far as I understood the weeks are stored in a customfield of type numbers) I suggest to use the value directly in the calculation (similar to what @Florian Bonniec already mentioned)

some important points to mehtion regarding this solution:

I tested this in a DC and found out that values of numbers fields are stored/returned as float/with digit:

see my example- the field "Effort" is a customfield of type Number and filled with value "3"

so the following line:

weeks: {{issue.Effort}}

returns into:

weeks: 3.0

Therefore the calculation with only using the numbers value in .plusWeeks() failed too.

Nevertheless this can be solved with using the "floor" function to numbers. So the following line in the "Edit issue" action worked for me and the Due Date was updated correctly (replace the "Effort" with your specific customfield´s name):

{{issue.start Date.plusWeeks(issue.Effort.floor)}}

Please let me know if this helps.

Best
Stefan

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

jira-data-center

data-center