The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Why does my script just delete the destination issue due date instead of changing it?

Imogen Caroline Brendel
August 10, 2021

I am trying to replicate MS Project schedule modeling ability in Jira. I figured out how to have a ticket's start move to be 1 business days after the blocker's due date:

IF trigger issue due date changes

THEN for blocks start date set to: {{triggerissue.duedate.plusBusinessDays(1)}}

That works well!

But now I want the due date on the destination issue to be the field change to the start date of the destination issue caused by the above. I can't figure out what to put in?

So I currently have:

IF trigger issue due date changes

THEN for blocks: started date set to {{triggerissue.duedate.plusBusinessDays(1)}}

AND due date set to {{targetissue.startdate.fieldchange}}

The last bit just empties out the due date field! Why? What am I doing wrong?

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Nir Haimov
Community Champion
August 11, 2021

Hi @Imogen Caroline Brendel 

first, add a "log" action to print the data you are actually trying to set to the field.

second, make sure the data you send is what the destination field can accept.

Usually this behaviour happens when you try to send data in format the field not accept, so the field value is cleared instead.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events