Product feedback
Suggest an improvement, explain confusing behavior, or describe what would make a module more useful.
Contact and product feedback
Help shape ByteCase around real examiner work.
Submit product feedback, testing results, workflow problems, documentation requests, resource suggestions, or collaboration ideas for ByteCase.
What happens next
Your message is reviewed by a person.
Product feedback may influence the roadmap, documentation, validation priorities, or individual module design. A response is not guaranteed, but useful testing details and reproducible problems are especially valuable.
Looking for a Hub license?
Create the .bcreq request in Hub and email the saved attachment for manual review. This feedback form does not issue licenses or accept license request attachments.
Read the email license instructions →Useful submissions
What belongs here.
Testing results
Share the operating system, ByteCase version, steps performed, expected result, and observed result.
Workflow problems
Identify repetitive documentation, verification, review, handoff, validation, or case-organization friction.
Resources and collaboration
Recommend a durable examiner reference, propose a guide, or discuss contributing to the project.
Send a message
Give enough context to make the feedback actionable.
Plain language is fine. For software problems, include the steps needed to reproduce the behavior. For workflow ideas, explain what examiners do now and where the process becomes repetitive, fragmented, or easy to miss.
Public software issue?
Reproducible bugs that do not contain sensitive information may be better suited for the applicable public GitHub repository.
Open ByteCase on GitHub →