# How to prevent assumed time in Date only fields?
**URL:** https://discuss.elastic.co/t/how-to-prevent-assumed-time-in-date-only-fields/76320
**Category:** Kibana
**Created:** [February 23, 2017, 10:16pm UTC](https://discuss.elastic.co/t/how-to-prevent-assumed-time-in-date-only-fields/76320 "2017-02-23T22:16:13Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@cbcb](https://discuss.elastic.co/u/cbcb)
#### Post date: [February 23, 2017, 10:16pm UTC](https://discuss.elastic.co/t/how-to-prevent-assumed-time-in-date-only-fields/76320/1 "2017-02-23T22:16:14Z")
We are having trouble with Kibana presenting the wrong dates to our users as its doing background UTC conversions that we do not want to have happen as this then presents invalid dashboard results to users in multiple time zones. We are seeing {Date-1} values which is not matching against what is collected and stored in Elastic Search JSON as {Date}.
We have tried several index mapping definitions.
...
"date1" : { "type" : "date","format":"strict\_date"},
"date2" : { "type" : "date","format":"basic\_date"},
...
Our JSON values we tried are in "yyyy-MM-dd" or "yyyyMMdd" format as per the ES API expectation of value format.
We have other index fields for date time, and the UTC to browser conversion, makes sense in those situations, but not for situations where date is provided.
So we don't understand the assumption of time interpretation by Kibana when none is provided and recalculating results. Is there a way to prevent this assumption of time by Kibana for only date fields?
---
### Author:  [@Bargs](https://discuss.elastic.co/u/Bargs)
#### Post date: [February 23, 2017, 11:32pm UTC](https://discuss.elastic.co/t/how-to-prevent-assumed-time-in-date-only-fields/76320/2 "2017-02-23T23:32:54Z")
That's a great question @cbcb. We don't currently have a way to handle basic dates in Kibana. I went searching for existing Github issues but I was surprised to come up empty handed. Would you mind filing an enhancement request describing your usecase?
> **[Build software better, together](https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Felastic%2Fkibana%2Fissues%2Fnew)**
>
> GitHub is where people build software. More than 27 million people use GitHub to discover, fork, and contribute to over 76 million projects.
---
### Author:  [@cbcb](https://discuss.elastic.co/u/cbcb)
#### Post date: [February 24, 2017, 8:30pm UTC](https://discuss.elastic.co/t/how-to-prevent-assumed-time-in-date-only-fields/76320/3 "2017-02-24T20:30:36Z")
Thanks for looking into this Matt and confirming that there is nothing out there.
I did follow your recommendation and create an issue in github. Not sure if I can define label as enhancement, but at least its posted for a mediator to assign correct path, if I don't have permission.
>
---
### Author:  [@Bargs](https://discuss.elastic.co/u/Bargs)
#### Post date: [February 24, 2017, 8:53pm UTC](https://discuss.elastic.co/t/how-to-prevent-assumed-time-in-date-only-fields/76320/4 "2017-02-24T20:53:18Z")
Thanks much @cbcb, I've labeled the issue and assigned it to the proper functional area.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 24, 2017, 8:53pm UTC](https://discuss.elastic.co/t/how-to-prevent-assumed-time-in-date-only-fields/76320/5 "2017-03-24T20:53:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.