Hi All,
I have a custom "Date Accepted" field and "Date completed" field on Jira cloud and will like the Date completed field to be updated with by adding few days e.g 2 days to any value entered in the Date accepted field
Can anyone help with this?
You can use Automation. Have you attempted this? Here is a link to the docs around working with date fields to assist - smart-values-date-and-time-functions
Thanks for the update but I did look into the option of automating this however it is not returning the value I need. I tried this but it does not return any value
{{issue.[Date Accepted].plusBusinessDays(10)}}
I want WO ETA value to be the value entered in Date Accepted +10 days
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Seun Mustapha -- Welcome to the Atlassian Community!
Please try to remove the square brackets around the smart value:
{{issue.Date Accepted.plusBusinessDays(10)}}
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
that should do it i think
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Celyn -- Welcome to the Atlassian Community!
Please consider posting an image (and/or the smart values) you tried. That will provide context for the community to offer ideas. Thanks!
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill, we figured it out. The syntax provided above did not work for us. Once we changed the syntax to quotation marks the rule worked.
{{"Estimate Delivery Date".plusbusinessdays(10)}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Celyn.
I am glad you got it to work...and...I have not seen consistency in automation rules of when the quotation marks around custom field names are needed/not needed. The fallback when neither seems to work is to use the custom field ID number instead, such as: {{issue.customfield_12345}}
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.