A Board for Leaving Feedback as Posts and Checking Progress Context
Instead of a short inquiry form, we set up a board format with titles and body text for leaving feedback and checking content again in list and detail pages.
Product improvement requests are often hard to understand the cause and expected result from a single sentence. We provided /feedback as a board format so that usage environment, reproduction steps, and expected behavior can be left together.
Good feedback is not briefly collecting complaints but leaving records that allow re-checking the context where the problem occurred.
What Changed in This Update
- You can write feedback titles and detailed body text.
- You can find written feedback again in the list and check detailed content.
- You can leave bug reports, feature requests, and usage experiences specifically rather than mixing them into a single sentence.
- We guide what information operators need to check and what information should not be made public.
- We laid the groundwork for providing clearer replies and processing status in the future.
How to Verify
- Search existing posts at /feedback to check if the same problem exists.
- Write a title that indicates the problem type.
- In the body, separately describe the occurrence environment, reproduction steps, actual result, and expected result.
- Remove personal information, tokens, and private conversation originals before submitting.
Example in Actual Usage Flow
For example, when the user checks the current improvement status, they search existing posts at /feedback to check if the same problem exists. They write a title that indicates the problem type. Then they remove personal information, tokens, and private conversation originals before submitting. In this process, the following scope should not be confused with the current completion status. Board submission does not guarantee immediate fixes or implementation. Checking this way helps distinguish between already provided features and parts still being stabilized.
Before and After the Change
Before the improvement, the currently provided scope and parts still being stabilized could appear mixed within a single sentence. In this update, instead of a short inquiry form, we set up a board format with titles and body text for leaving feedback and checking content again in list and detail pages. Already provided features are preserved as is, and only improvement targets are described separately so users can understand the current status without exaggeration.
Scope and Things to Note
- Board submission does not guarantee immediate fixes or implementation.
- Public posts should not include account passwords, authentication tokens, or private conversation originals.
- The number of feedback items does not automatically determine priorities; risk level and contract impact are reviewed together.
- Payment, authentication, and data issues require a separate verification process from general feature requests.
Why This Change Matters in the Overall 5BY.AI Structure
The feedback board is not a feature for scoring user opinions but a record channel to ensure the product does not lose actual usage context. When information that can reproduce problems accumulates, the initial inconsistency boundary can be found based on evidence rather than speculation.
Criteria for Verifying This Update
- The scope being improved and the scope already stably provided should not be mixed in the same sentence.
- UI and Provider compatibility improvements should not change the memory Core's storage units and user choice contract.
- Items not yet completed should not be expressed as currently provided features and should be updated in subsequent updates.