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

[Rainer Montag]

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, 

   Rainer

[Rainer Montag · Accepted solution]

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

- https://jira.atlassian.com/browse/JPOSERVER-2358

- https://jira.atlassian.com/browse/JRASERVER-41646