# Saving time filter for a user session

**URL:** <https://discuss.elastic.co/t/saving-time-filter-for-a-user-session/111621>\
**Category:** Kibana\
**Created:** [December 13, 2017, 6:08pm UTC](https://discuss.elastic.co/t/saving-time-filter-for-a-user-session/111621 "2017-12-13T18:08:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shwetank](https://avatars.discourse-cdn.com/v4/letter/s/c6cbf5/32.png) [@Shwetank](https://discuss.elastic.co/u/Shwetank)\
**Post date:** [December 13, 2017, 6:08pm UTC](https://discuss.elastic.co/t/saving-time-filter-for-a-user-session/111621/1 "2017-12-13T18:08:02Z")

</div>

Hi,

Is there a way to save time filter selection for a user session.

**Use case :**

We have navigation from one dashboard to another using markdown.

Dashboard were saved initially with time selection for e.g. last 24 hrs.  
If a users wants to search data for a particular time window which they select in first dashboard, but then moves onto second dashboard for more granular information, time changes back to saved time from dashboard i.e 24 hrs in this case.

Thus every time user have to change the time selection.

Even the \> timeRestore property doesn't help as setting it false defaults the time selection to value set in **timepicker:timeDefaults**

I tried setting **state:storeInSessionStorage** to true, but I believe it is for some different purpose.

it becomes very irksome to change time if you have many navigation and you are trying to focus on a particular time window.

Thanks,  
Shwetank

---

<div class="post-metadata">

**Author:** ![spalger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spalger/32/14092_2.png) [@spalger](https://discuss.elastic.co/u/spalger)\
**Post date:** [December 14, 2017, 8:10pm UTC](https://discuss.elastic.co/t/saving-time-filter-for-a-user-session/111621/2 "2017-12-14T20:10:21Z")

</div>

When you put the dashboard in the markdown, ensure it doesn't have the `_g` query string parameter. If it is not there then the current "global state" will be used, and the time filter will persist when using the link.

---

<div class="post-metadata">

**Author:** ![Shwetank](https://avatars.discourse-cdn.com/v4/letter/s/c6cbf5/32.png) [@Shwetank](https://discuss.elastic.co/u/Shwetank)\
**Post date:** [December 19, 2017, 5:16pm UTC](https://discuss.elastic.co/t/saving-time-filter-for-a-user-session/111621/3 "2017-12-19T17:16:13Z")

</div>

Thanks Spencer, I'll try and update on this thread.

---

<div class="post-metadata">

**Author:** ![Shwetank](https://avatars.discourse-cdn.com/v4/letter/s/c6cbf5/32.png) [@Shwetank](https://discuss.elastic.co/u/Shwetank)\
**Post date:** [December 19, 2017, 5:51pm UTC](https://discuss.elastic.co/t/saving-time-filter-for-a-user-session/111621/4 "2017-12-19T17:51:39Z")

</div>

> [@spalger](#):
>
> , ensure it doesn't have the \_g query string parameter

I checked the markdown we have,  
it is like this

```
&nbsp;
## **[&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;System 1](/#/dashboard/468f07e0-b03a-11e7-bc29-ad524d58b343)**

```

Then on the landing screen, they are like this

`### **[_Release A_](/#/dashboard/42aa3b10-a22d-11e7-a2a3-756511b4ea73)**`

**We do not have \_g paramter.** _I quoted just a couple, but its same in all of them._

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 16, 2018, 5:52pm UTC](https://discuss.elastic.co/t/saving-time-filter-for-a-user-session/111621/5 "2018-01-16T17:52:23Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.