# Refresh button for Reports

**URL:** https://discourse.notenik.app/t/refresh-button-for-reports/375
**Category:** Feature Requests
**Created:** [December 13, 2023, 10:56pm UTC](https://discourse.notenik.app/t/refresh-button-for-reports/375 "2023-12-13T22:56:24Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Malcolm](https://discourse.notenik.app/letter_avatar_proxy/v4/letter/m/e19b73/32.png) [@Malcolm](https://discourse.notenik.app/u/Malcolm)
#### Post date: [December 13, 2023, 10:56pm UTC](https://discourse.notenik.app/t/refresh-button-for-reports/375/1 "2023-12-13T22:56:24Z")

</div>

Does it make sense to refresh a report?

I’ve set up a few reports. Some are static snapshots. Other reports are volatile. My personal to-do list is a report arranged by priority ( status ) and seq. This report gets stale very quickly. Some tasks only take a few minute to perform and document. Some tasks change priority, some get blocked, some generate new tasks which have can have higher priority than other things on my list. All these mean that my to-do list needs to be updated. I’d like to be able to Refresh the existing report, rather than close it and then create a new report.

---

<div class="post-metadata">

### Author: ![hbowie](https://discourse.notenik.app/user_avatar/discourse.notenik.app/hbowie/32/6_2.png) [@hbowie](https://discourse.notenik.app/u/hbowie)
#### Post date: [December 19, 2023, 10:50pm UTC](https://discourse.notenik.app/t/refresh-button-for-reports/375/2 "2023-12-19T22:50:54Z")

</div>

This sounds like a good suggestion. I’ll try to find some time to work on this.

---

<div class="post-metadata">

### Author: ![hbowie](https://discourse.notenik.app/user_avatar/discourse.notenik.app/hbowie/32/6_2.png) [@hbowie](https://discourse.notenik.app/u/hbowie)
#### Post date: [December 28, 2023, 2:31am UTC](https://discourse.notenik.app/t/refresh-button-for-reports/375/3 "2023-12-28T02:31:29Z")

</div>

See the [latest beta](https://discourse.notenik.app/t/beta-version-13-6-3-available-for-testing-on-december-27th-2023/383) and let me know how this works for you!

---

<div class="post-metadata">

### Author: ![Malcolm](https://discourse.notenik.app/letter_avatar_proxy/v4/letter/m/e19b73/32.png) [@Malcolm](https://discourse.notenik.app/u/Malcolm)
#### Post date: [December 28, 2023, 2:34am UTC](https://discourse.notenik.app/t/refresh-button-for-reports/375/4 "2023-12-28T02:34:56Z")

</div>

I’ll load and test,

thank you.

- Tests passed

---

<div class="post-metadata">

### Author: ![Malcolm](https://discourse.notenik.app/letter_avatar_proxy/v4/letter/m/e19b73/32.png) [@Malcolm](https://discourse.notenik.app/u/Malcolm)
#### Post date: [January 17, 2024, 3:10am UTC](https://discourse.notenik.app/t/refresh-button-for-reports/375/5 "2024-01-17T03:10:42Z")

</div>

Thanks for implementing this. It’s definitely easier.

This afternoon I noticed that I had about a dozen windows named “Script Output.” This reflects the number of times I updated that report today. I was a little surprised because I had thought the report was updating within the same window.

I wouldn’t call this a bug, but I wonder whether you think that it makes more sense to re-use the same window?

---

<div class="post-metadata">

### Author: ![hbowie](https://discourse.notenik.app/user_avatar/discourse.notenik.app/hbowie/32/6_2.png) [@hbowie](https://discourse.notenik.app/u/hbowie)
#### Post date: [January 17, 2024, 4:27am UTC](https://discourse.notenik.app/t/refresh-button-for-reports/375/6 "2024-01-17T04:27:13Z")

</div>

Let me look into this.

---

<div class="post-metadata">

### Author: ![hbowie](https://discourse.notenik.app/user_avatar/discourse.notenik.app/hbowie/32/6_2.png) [@hbowie](https://discourse.notenik.app/u/hbowie)
#### Post date: [January 18, 2024, 9:59pm UTC](https://discourse.notenik.app/t/refresh-button-for-reports/375/7 "2024-01-18T21:59:00Z")

</div>

See the [latest beta](https://discourse.notenik.app/t/beta-version-13-7-3-available-for-testing-on-january-18th-2024/397). This should fix the problem.
