We have a Plan allowing users to edit the [system] Due date field. When an Initiative reaches a milestone, the Due date is stored in the End Date field so we have a baseline to compare against when the work is complete.
My automation sets the End Date to the Due date.
Doing a search for the updated Issue, the dates are different. The End Date appears to be 5 hours behind, presumably to adjust to CST. I assume this is because the difference between Date and Datetime fields. I've tried applying the addHours function (I'm Data Center) and even the cloud plusHours function, but neither seem to work.
Any advise is MUCH appreciated!
Thanks in advance,
Steve
Instead of using a smart value, select the 3 dots on the right side of the field and choose the COPY option.
Then select the Due date from the trigger issue.
I hope tis answers your question
Did my proposed solution help you with achieving your goal?
If so please accept my answer.
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.
I guess I'm perplexed why there is a difference when using the smart value versus copying.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Steve Tedeschi ,
i would happy to help you though im struggling to understand what you are trying to achieve here why did you make the end date field a datetime field when the information youre storing in it comes from a date field ? that already strikes me as kind of odd. Then im also unsure of what target end is in this case.
Best regards
Henning
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, using Jira template and cannot control date v datetime configurations.
The search results screenshot showed a couple date/datetime fields. Sorry if Target End Date lead to confusion.
While @Marc - Devoteam's solution worked, I'm curious how you could modify the value, instead of copying.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Steve Tedeschi i would have just created a new customfield which is a date field aswell and then used the smart value of that due date and write that into the datefield with the smartvalue {{issue.duedate}}.
Thats also why i dont understand your comment with the jira template and not being able to change it. You can edit the template and add your own customfield over the administration -> issues -> customfields -> date field.
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.