Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Incomplete message #174

Open
osfanbuff63 opened this issue Oct 1, 2021 · 3 comments
Open

Update Incomplete message #174

osfanbuff63 opened this issue Oct 1, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@osfanbuff63
Copy link
Member

osfanbuff63 commented Oct 1, 2021

Umjia has been using an updated Incomplete message, and I think we should update the current incomplete message to add this information.

*Thank you for your report!*
However, this issue is {color:#FF5722}*Incomplete*{color}.

Your report does not contain enough information. As such, we're unable to understand or reproduce the problem.

You are welcome to create a new ticket about your issue with more detailed information.
However, please review the Bug Tracker Guidelines and be sure to search for existing issues before writing a new bug report.

Please note that issues on consoles should be reported in the *MCPE* project.
You may find this [*Report Creation Form*|aka.ms/BedrockBug] helpful for any future reports you create.

(quick-links)
@osfanbuff63 osfanbuff63 added enhancement New feature or request discussion needed labels Oct 1, 2021
@osfanbuff63
Copy link
Member Author

But there's two parts that are specific to MCPE/BDS, the console part and the aka.ms link (the aka.ms link changing between project)

@MikeUnverferth
Copy link
Contributor

I don't think the mention of consoles is needed as that is only meaningful for the rare cases where an issue was reported in the wrong project and is also incomplete.

The aka link is project-specific though, so we would need different messages for MC vs MCPE.

@MikeUnverferth
Copy link
Contributor

It might be more useful to add a little more detail about what is needed in a report. Something like:

Reports should generally include a list of steps to reproduce the bug, along with both Observed and Expected behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants