Repository navigation
Improve the documentation on the whole three-parted-issue-tracker thing #8288
Closed
alexanderadam
started this conversation in
General
Replies: 1 comment
|
This was a leftover from the Wiki.js 2.x workflow which was very different. Issues are opened once again now. About not being redirected to the feedback page after login, this is expected and is the result of you clicking the Login button instead of the Submit Idea or Upvote button. Use either of the latter and you'll be redirected back to the feedback page. Also, please write your own post next time. This could have been 1 short paragraph instead of the unnecessary detailed thesis you generated with AI. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello
first of all, thank you for all the work you put into Wiki.js. I'd like to share some feedback on how bugs, issues and feature requests are currently reported and tracked. I found the process hard to navigate and I guess that I'm not the only one. 😉
Most GitHub users go straight to the Issues tab to search for or file an issue. Wiki.js currently has 7 open issues. The explanation of the reporting process is in the last one, and it isn't pinned:
This is not the whole picture, though. Feature requests do not count as "any other topic": they're tracked outside of GitHub.
Users only find this out from the pinned discussion.
When they follow that link and sign in with the Login button, they're sent to
https://docs.js.wiki/instead of back tohttps://docs.js.wiki/feedback.So instead of clicking New issue and starting to write, a user currently has to:
https://docs.js.wiki/feedbackmanuallyI understand this. Yet, GitHub has decent good tools to handle it.
The repo already uses
.github/ISSUE_TEMPLATE/and there are triage tools such as issue-labeler or agentic issue triage that help filter out support requests and misconfigurations.Discussions work well for discussions but for anything related to code or status they are not great:
At first I assumed that discussion states reflected implementation status.
That doesn't seem to be applied consistently:
That last one admits there's a bug but suggests it won't be tracked, which is confusing for users.
As a result, related information ends up spread across several places. Take MCP:
This makes it hard to connect the patches to the bugs and requests they fix. For example, the related commit doesn't reference any GitHub issue, feedback item or discussion.
To follow a single topic, users have to check four places: the issue tracker, Discussions, the feedback platform and the Git history. You probably have your own way of tracking this. For contributors and people evaluating Wiki.js, though, it's hard to follow.
Even without changing the overall process, a few small steps would help a lot:
/feedback.Thanks for considering this
All reactions