Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,473
Community Members
 
Community Events
176
Community Groups

Error parsing date string when trying to copy one date field from another

Edited

I've put in a place an automatic rule that where a date custom field takes (start date) the value of another date field (Sprint Start Date). I've been getting this error:

BDDN-265 (Error parsing date string: Fri Sep 18 18:00:00 CEST 2020 (customfield_11603), Error parsing date string: Mon Sep 07 08:00:00 CEST 2020 (customfield_11602), Error parsing date string: Fri Sep 18 18:00:00 CEST 2020 (customfield_11605), Error parsing date string: Mon Sep 07 08:00:00 CEST 2020 (customfield_11604))

Our Jira is configured in french and I suspect it has something to do with that. Any idea how I can fix this?

 

Here's the rule (in french) and its translation below:

Error.PNG

 

The translation :

When : the value of the Sprint field changes

  If : Sprint is in openSprints() (JQL request)

  If : Epic Link is different than "Formations2020"

  And : "Due Date" is NULL

  And : date of issue creation is less than Sprint Start Date

    Then : Modify the value of the following fields :

       Baseline start date takes the value of Sprint Start Date

       Start date takes the value of Sprint Start Date

       Baseline end date takes the value of Sprint End Date

       End Date takes the value of Sprint End Date

  Else-if : date of issue creation is greater than Sprint Start Date

  And : "Due Date" is NULL

  Then: Modify the value of the following fields :

       Baseline end date takes the value of Sprint End Date

       End Date takes the value of Sprint End Date

  Else-if : "Due Date" is not NULL

  Then: Modify the value of the following fields :

       Baseline end date takes the value of "Due Date"

       End Date takes the value of "Due Date"

[End of Rule]

 

The result of the audit log:

Error2.PNG

3 answers

1 accepted

1 vote
Answer accepted

I think I may have found a solution: ending every date with ".jiraDate" ( ex. {{sprint.startDate.jiraDate}} ). I gave it a try yesterday and it worked. I'll see if if doesn't bring any errors in the following days, but normally this should work. 

Give it a try @Matt Hewitt and let me if it works for you too.

What if a issue is spilled over to next sprint? the {{issue.Sprint.endDate.jiraDate}} is taking the Sprint end date of previous Sprint End Date.

 

How to get value of Current/ Active Sprint End date value?

0 votes
John Funk Community Leader Sep 16, 2020

Hi Iana - Welcome to the Atlassian Community!

Can you share the rule that you have so far? 

Error.PNG

The translation :

When : the value of the Sprint field changes

  If : Sprint is in openSprints() (JQL request)

  If : Epic Link is different than "Formations2020"

  And : "Due Date" is NULL

  And : date of issue creation is less than Sprint Start Date

    Then : Modify the value of the following fields :

       Baseline start date takes the value of Sprint Start Date

       Start date takes the value of Sprint Start Date

       Baseline end date takes the value of Sprint End Date

       End Date takes the value of Sprint End Date

  Else-if : date of issue creation is greater than Sprint Start Date

  And : "Due Date" is NULL

  Then: Modify the value of the following fields :

       Baseline end date takes the value of Sprint End Date

       End Date takes the value of Sprint End Date

  Else-if : "Due Date" is not NULL

  Then: Modify the value of the following fields :

       Baseline end date takes the value of "Due Date"

       End Date takes the value of "Due Date"

[End of Rule]

John Funk Community Leader Sep 17, 2020

Thanks! One more share - can you show the value of one of the Alors details? 

I am suspicious about the CEST being in the middle of your date that is being parsed. I believe that is what is causing it to error out. 

Is this what you mean?

Error4.PNG 

John Funk Community Leader Sep 17, 2020

try using this and see if it helps:

{{sprint.startDate.shortDate}} where you add .shortDate to each smart value. 

I really think there is a bug. 

Will do. BTW, I should have mentioned, this rule used to work perfectly. But I updated the Automation plug-in at the beginning of this week and it is since then that it started bugging. 

John Funk Community Leader Sep 17, 2020

What did you change about the rule from when it was working? 

I changed the trigger. It used to be At the beginning of every sprint and then applied a branch rule to all issues in the sprint. But that didn't take into account issues that were created (or added to the sprint) after the beginning of the sprint. I also added the if sprint is not empty condition and the sprint is in opensprints() JQL query. I didn't change anything in the Alors details. They were set in the exact same way since I created the rule.

John Funk Community Leader Sep 17, 2020

It might have introduced the error due to a but with the dates getting applied under teh branch. 

Give the shortDate a try and if it fails, you should open a support ticket. 

I've tested and it still doesn't work. It still doesn't recognize the date despite the change to short form. Below the error:

PTD-10 (Error parsing date string: 8/7/20 (customfield_11603), Error parsing date string: 7/31/20 (customfield_11602), Error parsing date string: 8/7/20 (customfield_11605), Error parsing date string: 7/31/20 (customfield_11604))

I'll open a support ticket. Thanks for your help.

Like # people like this

HI Iana: I've encountered same issue with Error parsing data string.

If you don't mind sharing, what is the support ticket status on resolution?

Thanks

Hi Matt, I've had no reply by Jira's support team so far. 

Like Matt Hewitt likes this

Hi @Iana Encarnacion  - You haven't received an initial response from support? When did you submit it?

Can you share the support id?

Hi @John Funk ,

Besides the automatic response confirming the support ticket was registered, none.

Here's the support id:  GHS-200779

Like Dave Liao likes this
John Funk Community Leader Sep 22, 2020

Thanks - when did you initially submit it?

Just after your suggestion last thursday Sept. 17th

Diego Atlassian Team Sep 23, 2020

Hello there @Iana Encarnacion  and @John Funk !

I reached out to our internal teams and they have been facing a severe overload of tickets for the past few days. I made sure that they are aware of your ticket @Iana Encarnacion  and they will surely look into it.

Thanks for reporting this for us.  

I think I may have found a solution: ending every date with ".jiraDate" ( ex. {{sprint.startDate.jiraDate}} ). I gave it a try yesterday and it worked. I'll see if if doesn't bring any errors in the following days, but normally this should work. 

Give it a try @Matt Hewitt and let me if it works for you too.

Thanks for your help @John Funk and @Diego .

Like # people like this

This worked for me as well. Thank you.

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events