Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automating a custom "Time Stamp" field to set its value to "x days" from the triggerissue's same val

Shaye Murray January 10, 2023

Hey folks!

I've burned so much time on this, I hope I'm just missing something silly

Intended Behaviour:
Once a given issue is transitioned to DONE, CLONE it. And update the Clone Issue's customfield (it's a "Time Stamp" field, in a Team-Managed Project), so that it's seven days from the triggerissue's same customfield's value.

Some points to clarify:

  1. Rule Audit Log registers the automation as a "success".

  2. I've tested and confirmed that the smart value works for copying the value. I've even tried adding a second step that does the "add seven days" action. The issue's History Log indicates that it copies correctly, but when the 'edit' action happens, it just erases the value.

  3. I've tried appending a number of {{... .[dateformats]}} to the end, such as "jiraDate".

  4. I've had no issues in the past doing this with a simple "Date" field type using smart values.

  5. I've tried both the MyFieldName (seen below) and the customfield_12345 formats.

r/jira - Automating a custom "Time Stamp" field to set its value to "x days" from the triggerissue's same value (What am I missing??)

Any help here at all would be mana from the gods. Thanks Friends!

1 answer

0 votes
Mark Segall
Community Champion
January 11, 2023

Hi @Shaye Murray and welcome to the community!

One thing I'm seeing in your smart value is that you have "CheckTime", but the field name appears to be "Check Time".  Try this:

{{triggerIssue.Check Time.plusWeeks(1)}}
Shaye Murray January 11, 2023

Thanks for the response @Mark Segall

Your suggested format (I tried that format throughout my testing), yields the same result, I'm afraid.

Mark Segall
Community Champion
January 11, 2023

Can you please share a screenshot of one of the failed entries in the audit log? 

Shaye Murray January 11, 2023

That's thing thing, Mark. The Audit Log regards each instances of the rule as a success. You'll see below that I modified the rules to edit the Checktime after the issue is created; I did this to see the issue's edit history (attached).

Screen Shot 2023-01-11 at 13.19.25.png

Screen Shot 2023-01-11 at 13.21.28.png

Thanks, again @Mark Segall .

Mark Segall
Community Champion
January 11, 2023

Ahh - In your original screenshot I didn't see the extra edit action after the clone is created.  So, you're trying to set the check time both during creation and after and neither are working?  

Let's try this... Add a Log Action just before you clone the issue with the following:

Trigger Check Time: {{triggerIssue.Check Time}} ** Trigger Issue Check Time +1w {{triggerIssue.Check Time.plusWeeks(1)}}

Then execute another test.  Let's just validate what it is retrieving for Check Time and what happens when we add a week to it. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events