# Suggestion for "OnDemand's known issues"

**URL:** <https://discourse.openondemand.org/t/suggestion-for-ondemands-known-issues/1614>\
**Category:** General Discussion\
**Tags:** doc-request\
**Created:** [August 3, 2021, 5:42pm UTC](https://discourse.openondemand.org/t/suggestion-for-ondemands-known-issues/1614 "2021-08-03T17:42:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![azric](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/azric/32/63_2.png) [@azric](https://discourse.openondemand.org/u/azric)\
**Post date:** [August 3, 2021, 5:42pm UTC](https://discourse.openondemand.org/t/suggestion-for-ondemands-known-issues/1614/1 "2021-08-03T17:42:45Z")

</div>

On [OnDemand’s Known Issues — Open OnDemand 2.0.13 documentation](https://osc.github.io/ood-documentation/latest/issues/overview.html) in the left pane is “OnDemand’s Known Issues”. Example " Viewing large files causes problems". I read this and other “Known Issues” as “new problems with OOD 2.x”, which a) has scared me away from upgrading, and B) is plain wrong. This particular problem dates back to 2017 which predates version 1.3.0.

I would find it helpful if the OOD version the problem was reported against was included with each item which would avoid the misconception that these issues are “new with the current product” as opposed to lingering artifacts.

---

<div class="post-metadata">

**Author:** ![westburg.2](https://avatars.discourse-cdn.com/v4/letter/w/0ea827/32.png) [@westburg.2](https://discourse.openondemand.org/u/westburg.2)\
**Post date:** [May 26, 2022, 4:13pm UTC](https://discourse.openondemand.org/t/suggestion-for-ondemands-known-issues/1614/2 "2022-05-26T16:13:59Z")

</div>