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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Setting custom field "Target end" via REST API: Timezone problem?

Hello, we are using

Jira Server 7.13.9

Portfolio for Jira 3.14.0

Default User Timezome in Jira: (GMT+01:00) Berlin


I have a problem setting the custom field "Target end" via Jira REST API, that the date set ist always shown one day behind:

1) When I create an issue using REST POST /rest/api/2/issue, I set e.g.

        "customfield_10901": "2019-11-28T14:00:00.000+0000",

 where customfield_10901 ist the "Target End" field

2) After creating, the UI shows me "27/Nov/19" and the REST GET /rest/api/2/issue/{key} is returning

"customfield_10901": "2019-11-27",


For me it looks like a issue with converting the timestamp, especially:

- time information is ignored and set to "00:00:00" (?)

- 00:00:00 GMT+1 is converted to 23:00:00 UTC the day before (?)

- the day before is stored and shown in Jira (?)


I also try to set

        "customfield_10901": "2019-11-28",

but the same result it is shown in UI and REST as 27.


Can anybody confirm this, if this is a bug in the Portfolio Plugin?


Thanks in advance, 



1 answer

1 accepted

0 votes
Answer accepted

I got the confirmation, that this is a known issue in Jira and Portfolio:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events