--- title: "Closing issues because they are unplanned is bad UX" url: https://daily.dev/posts/closing-issues-because-they-are-unplanned-is-bad-ux-ce8rzyrif source_url: https://advancedweb.hu/shorts/closing-issues-because-they-are-unplanned-is-bad-ux/ type: article source: "Advanced Web Machinery" published: 2025-12-15T20:39:06.566Z updated: 2025-12-15T20:39:29.118Z tags: ["open-source", "github", "project-management"] reading_time: 3 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Closing issues because they are unplanned is bad UX **[Advanced Web Machinery](https://daily.dev/sources/advancedweb)** · 3 min read · 0 upvotes · 0 comments ## Summary Closing unplanned issues creates poor user experience because reporters lose visibility when features are eventually implemented. When issues are closed as "not planned" and later addressed in separate tickets, original reporters miss notifications and must actively search for fixes. A better approach is keeping issues open with tags for filtering, preserving the backlog as a record of known gaps and bugs that may become relevant later. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#open-source](https://daily.dev/tags/open-source), [#github](https://daily.dev/tags/github), [#project-management](https://daily.dev/tags/project-management) [View this post on daily.dev](https://daily.dev/posts/closing-issues-because-they-are-unplanned-is-bad-ux-ce8rzyrif)