When you're trying to type 'mji-outage' for a quick message, it gets replaced with the 'outdated client' message due to 'mji-out'

Messages for performance measurements are no longer up to date (e.g. replace /debug with /perf etc)

Background

I'm trying to make the deploy process of this tool automated by using GitHub Actions with the github-pages-deploy-action.

We need a token that has permission to write to the repository.

The Problem

GitHub automatically creates a GITHUB_TOKEN secret that we can use in the workflow. However, I just figured out that the GITHUB_TOKEN couldn't trigger a GitHub Pages build according to JamesIves/github-pages-deploy-action#5.

Therefore, we have to add a personal access token that has write access to this repo. The thing is that only members with admin permission can create GitHub action secrets, so I'm opening this issue looking for help.

To Resolve

1. Create a personal access token that has write permission (I guess?) to this repo.
2. Add that token to this repo's secrets. The name of this secret should be ACCESS_TOKEN, the value of it should be the token generated in the first step.
3. Merge #22.

The "Provide affected version" could possibly be improved. Here are some ideas, the ones where I am not sure how useful they are are marked with a ❓. Feedback is appreciated.

1. Add period after "We have removed it and added the latest released version"
2. Move "We have removed it and added the latest released version" into panel or replace "it" with "the version". Since it is currently outside of the panel, the connection between "it" and "version" is possibly not obvious enough.
3. It might make sense to remove the panel. It feels a little bit weird that only some information is placed inside it, and it also does not match the format of other messages which have this structure ("This issue has been temporarily closed as..." and quicklinks section).
4. ❓ Clarify "You don't have access to them yet.". Obviously the user had access to the version in the sense that they were able to select it. Maybe something like the following would explain it better:

   Unreleased versions refer to versions which will be released in the future, but they are not available yet.

5. ❓ The message says "unreleased version", but the versions are called "future version" (though maybe not in all projects). Maybe it would be good to include the future version(s) which have been removed in the message?
6. ❓ Include the version which was added as replacement for the future version.

As shown by #121, the validation of the messages.yml file is currently not checking whether projects referenced in quick_links and messages have an entry in project_id.

Note however that mctest is at the moment referenced by messages despite having no quick_links and project_id entry.

Basically should behave same as if the Copy button is pressed. Saves step of switching between keyboard and mouse.

Wondering adding "realms" broke it or something else? I was assuming the web app just got the list from the json file but maybe not?

Shorten label from "Technical Support issue" at the same time.

Now that Dungeons and Legends are closed for new bug reports, these should be removed from the "Wrong Project - Moved" message.

Also, the Invalid / Wrong Project message should be removed entirely. Instead of asking the reporter to create another issue, just use the Wrong Project - Moved message and "move" the issue accordingly. If not authorized for that, submit request in appropriate channel for someone who is authorized to actually move it.

For further convenience to the bug tracker users, it would be nice if the bot would be able to respond to a user whose ticket it closed for being in a wrong language.

We need to decide:

• Do we want to translate the messages in the first place?
• To which languages should the message be translated?
• Who can translate the message?

For bedrock should this include links to the various places that purchase issues could occur, such as Google Play Store (Android), Apple App Store (iOS), Microsoft (Win10, Xbox), Sony PSN (PS4)?

Moved from #41

#41 added a warning to the readme. A similar warning should be added to the site itself

The bug

Arisa PR #725 changed the future version module by making it resolve reports as invalid rather than awaiting response, however the comment still contains the message 'This issue is being temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.'

Example Ticket

https://bugs.mojang.com/browse/MC-232220

Expected behavior

This message should be changed to reflect the new resolution

The Incomplete message for the REALMS project at least is now adding information related to a crash, that does not apply, at least not for bedrock realms.

This will shorten the selection list for the other projects.

Similar to https://bugs.mojang.com/browse/MCPE-94485?focusedCommentId=780028&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-780028

Recently we've been talking about a new helper message for invalid performance issues. Here is the message.

*Thank you for your report!*
However this report is *{color:red}Invalid{color}*

Performance drops are expected to happen between versions, especially in snapshots and betas. Simply stating that "My game is laggier" is not helpful for the bug tracker and for Mojang to diagnose your issue. If you can diagnose a specific cause when lag happens for you, please open a new report for that specific issue. If you think this might be a hardware issue please head over to the *{color:#4C9AFF}[Minecraft Community Support Discord|https://discord.gg/58Sxm23]{color}* as they might be able to help with your issue.

Keep in mind that Mojang is constantly optimizing the game and simply playing the game provides feedback to Mojang on which parts cause performance issues. To learn more about this, head [here|https://www.minecraft.net/en-us/article/minecraft-snapshot-21w38a] for more information.
~Note that the information about telemetry only applies to Minecraft Java Edition. Bedrock still has telemetry though the data collected might be different~

*Quick Links*:
📓 [Bug Tracker Guidelines|https://aka.ms/MCBugTrackerHelp] -- 💬 [Community Support|https://discord.gg/58Sxm23] -- 📧 [Mojang Support|https://help.minecraft.net/hc/en-us/requests/new]
📓 [Project Summary|https://bugs.mojang.com/projects/MC/summary] -- ✍️ [Feedback and Suggestions|https://feedback.minecraft.net/] -- 📖 [Game Wiki|https://minecraft.fandom.com/wiki/Minecraft_Wiki]

A few messages use "Mojang Cusomter Support" while others including the quick links only use the term "Customer Support".
Maybe it would be good to make this consistent.

If I recall correctly this was discussed a little bit internally before and one argument for "Mojang Customer Support" was that it makes it more clear that this is the official support provided by Mojang.
What are your opinions?

The message for "Wrong project (moved)" doesn't include the REALMS project. We frequently move to REALMS if the issue is a server issue caused by realms, and not an issue with MC itself.

Change the outdated client message to say:

'However, this issue is Invalid.

Your Minecraft version is outdated. We currently take issues for the latest version and the latest snapshot.
Please update to the latest version as it includes the newest fixes. If you still have this problem after updating, then please create a new issue.
In case of a game crash, please also attach the crash report found in minecraft/crash-reports/crash--client.txt.

rather than:
However, this issue is Invalid.

Your Minecraft version is outdated. We currently take issues for version 1.20.1 and the latest snapshot.
Please update to the latest version as it includes the newest fixes. If you still have this problem after updating, then please create a new issue.
In case of a game crash, please also attach the crash report found in minecraft/crash-reports/crash--client.txt.

If you select a message which isn't in another project, and then switch to another project, it will turn the 'copy' button grey.

I could reproduce this using the 'account issue' message from the MC project, and then switching to the MCL project

The current experimental snapshot message is outdated still mentioning the 1.18 experimental snapshots. Updating the message like something shown below will make it so that future experimental snapshots won't need an updated message

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

We're currently not taking bug reports for experimental snapshots; it is for testing only. Please leave any new world generation-related feedback on the reddit post on [r/minecraft|https://www.reddit.com/r/Minecraft/comments/p1pc9d] or on the [feedback website|https://feedback.minecraft.net/hc/en-us].
If you experience this issue in the latest release please search for existing reports. If you did not find one, create a new report with the latest release as the affected version.

If you need help or support, you might like to follow a link below.

*Quick Links*:
📓 [Bug Tracker Guidelines|https://aka.ms/MCBugTrackerHelp] -- 💬 [Community Support|https://discord.gg/58Sxm23] -- 📧 [Mojang Support|https://help.minecraft.net/hc/en-us/requests/new]
📓 [Project Summary|https://bugs.mojang.com/projects/MC/summary] -- ✍️ [Feedback and Suggestions|https://feedback.minecraft.net/] -- 📖 [Game Wiki|https://minecraft.fandom.com/wiki/Minecraft_Wiki]

It would be nice to be able to have a general message about transient connectivity issues (realms, servers, marketplace) and resolve these as invalid, somewhat like the "crash logged automatically" ones. Every time there's a realms outage a bunch of reports get submitted and having to then collect them and resolve as a duplicate or ask if the problem is still happening takes quite a lot of time.
Proposed message text:

Thank you for your report.
Temporary connectivity and service availability issues related to Marketplace, Realms, and Servers, are handled by the team outside the bug tracker.
Check [Mojang Status|https://twitter.com/MojangStatus] for official announcements, or [Downdetector|https://downdetector.com/status/minecraft] for community reported outages.
If there is no general outage, you are free to create a new report, after searching for duplicate reports.
However, please first try to verify that the problem is not with your local connection or network settings. Visit [Minecraft Community Support|https://discord.gg/58Sxm23] for assistance.
You might also try to deactivate any VPN in use, and check your firewall settings. If your device supports mobile data, try switching to wifi.
[standard links]

BDS has its own "Wrong project" message, the only two differences are:

• It does not mention Dungeons
• It has an additional sentence about searching:

  Please don't forget to search for an existing issue matching yours in the appropriate project before raising a new one.

I think this additional sentence about searching would be quite useful in the already existing message for all other projects. Otherwise users will just create a duplicate in the other project.
Should we therefore add this sentence and then remove the BDS specific message?

Currently, it is often hard to find the correct message, with the increasing amount of messages and the dropdown becoming longer and longer as messages get added.
A possible solution to this could be to separate them into categories, by which they are sorted and maybe have some bold text as a separator in the dropdown (similarily to Jira:

This is also a possible alternate solution to #96, as certain applications could filter certain categories (and thus make Bot messages not appear on the site at all).

Possible categories could include:

• Duplicate
• Invalid
• Awaiting Response
• Panels / Notices
• Misc
• Bot messages

It would be very convenient if the application would show a preview field upon selection of a message. This way you can verify that you selected the intended message before you copy it, so that if you're a new helper or a forgetful one, you don't need to paste the message elsewhere before you know what message you're dealing with.

Additionally, if the message requires additional parameters, upon filling in any information for those, the preview field should automatically update and show the changes to the message with this information already included, without clicking any additional button. This way you can also instantly see what the extra information you fill in does to the message.

This would make the application more intuitively designed and slightly more convenient to use.

I imagine this preview field being a textarea that is javascript controlled. If it is left as editable, one could optionally manually modify/adjust the message before use, but that would preferrably also require a refresh button to reset said changes to what the form would produce by default.

It was internally suggested to include the /r/Mojira and Mojira Discord link to the quicklinks.

However, I am not sure if this is really needed because they will likely be only useful to a small number of users and having even more links in the quicklinks section might be confusing.

What are your opinions?

Currently the "Attach crash report" message only mentions that the user should attach the launcher_log.txt (though the Minecraft Hopper link describes how to copy the game log).

It would therefore be good to also describe where to find game logs (i.e. in the logs folder).
Additionally it might be good to get a separate Minecraft Hopper page because https://minecrafthopper.net/help/finding-minecraft-data-folder/ is only about the data folder (.minecraft) while crash reports and logs are in the profile / installation folder which could be somewhere else. Or we could additionally refer to https://minecrafthopper.net/help/guides/changing-game-directory/.

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)

Example here: https://bugs.mojang.com/browse/WEB-3078

'Issue guidlines' should link to the project summary, but instead links to here: https://bugs.mojang.com/projects/%project_id%/summary

Moved from mojira/arisa-kt#168

Currently, the language module is only in its testing phase. For when the module actually goes live, we should prepare the message that the bot uses when closing tickets not in English.
These messages should probably be translated to other languages too, for further convenience. We can translate to some languages ourselves (at least Spanish and German), but perhaps some Crowdin proofreaders might want to help out as well (cc @bemoty).

The current message for human moderators is this one:

*Thank you for your report!*
Thank you for taking the time to report a bug. Unfortunately we are only able to accept bug reports in English since it is the common language used on this tracker.

You are welcome to create a new ticket about your issue in English. You can use an online translator, if it helps.
However, we recommend making use of the [*+search feature+*|https://bugs.mojang.com/issues/] before writing a new bug report, as it's very likely that someone else already reported your issue before.
If you find an existing ticket about your issue, you can add a vote and any new information to it instead of reporting it yourself.

Please note that this bug tracker is not for support. If you have a payment issue or an issue with your account, please use the *Customer Support* link below.

*Quick Links*:
📓 [Issue Guidelines|https://help.mojang.com/customer/portal/articles/801354-writing-helpful-bug-reports-for-minecraft] -- 💬 [Community Support|https://discord.gg/58Sxm23] -- 📧 [Customer Support|https://help.minecraft.net/hc/en-us/requests/new] -- ✍️ [Feedback and Suggestions|https://feedback.minecraft.net/] -- 📖 [Game Wiki|https://minecraft.gamepedia.com/Minecraft_Wiki]

I propose that the "Quick links" are not translated because most links link to sites that are only in English. (Also note that Arisa is missing the "Feedback and Suggestions" link that was added to helper-messages recently; see also #139)

Before translating the message, perhaps it should be adapted in some way to make it more clear that the message comes from a bot, not from a human.

Currently, all bot messages have the following beneath the quick links:

~{color:#888}-- I am a bot. This action was performed automagically! Please report any issues in [Discord|https://discordapp.com/invite/rpCyfKV] or [Reddit|https://www.reddit.com/r/Mojira/]{color}~

Perhaps this message should be translated as well, but where should it be placed then?

This issue is for tracking progress on this rather long-term task:

1. Define what the message should say in English (in what way it should differ from the message used by humans, if at all)
2. Decide how the message should incorporate both the English and the translated message
3. Translate the final message into different languages

Based on this review comment.

The "Works As Intended" messages for all projects currently link to the version history wiki articles and /r/minecraftsuggestions:

The quick links already link to feedback.minecraft.net for suggestions so the /r/minecraftsuggestions link might be redundant.

1. Should the link to /r/minecraftsuggestions be removed from the "Works As Intended" messages?
   1.1 And should the quicklinks include a link to /r/minecraftsuggestions instead?
2. Should the version history links be removed (as suggested here by @violine1101) because they might not be that helpful?
3. Should the /r/minecraftsuggestions link of the "Feature request" message be removed as well?

Follow-up on #70 (because I missed that pull request)

1. Your report

   The module runs for all attachments, regardless of whether they were added by the reporter or anyone else.

2. with an invalid extension

   "invalid" might be mislead, maybe rather "not allowed"?

3. crashlogs

   "crash reports"

4. text files

   Maybe "text files ({{.txt}})" in case users think Word documents are text files

5. Please remember

   Sounds as if we told them somewhere about this already, even though we did not?

6. A period is missing after the last sentence.

7. Maybe it would be useful to include the name of the removed attachment, however that would be exploitable when users include Jira formatting code in their attachment names.

What do you think about changing the text to the following?

An attachment with a file extension, which is not allowed on this bug tracker, has been removed.

Executable files and word processing documents are not allowed as attachments.
Please attach crash reports, log files and screenshots as they are instead of pasting them into document.

For MCPE there are currently two messages for account issues:
contact-support:

Maybe it would make sense to remove the MCPE specific contact-support message and include the following in account-issue:

• Also for billing
• Use "Mojang Customer Support" instead of only "Customer Support" (see also #93)?

The messages mentioning Mojang or Community Support are currently not consistent:

• Most are using an article, but not all: "contact the support" vs. "contact support" (not sure what is the correct way, if any)
  • With article:

    • helper-messages/assets/messages.yml

      Line 358 in e7264d5

      -- If that did not help, please contact the *[Community Support|https://discord.gg/58Sxm23]*.

    • helper-messages/assets/messages.yml

      Line 373 in e7264d5

      -- If that did not help, please contact the *[Community Support|https://discord.gg/58Sxm23]*.

    • helper-messages/assets/messages.yml

      Line 459 in e7264d5

      If you need additional help to fix this problem, please contact the *[Community Support|https://discord.gg/58Sxm23]*

    • helper-messages/assets/messages.yml

      Line 664 in e7264d5

      Please check *MCL-6550* for help with your issue. If you still need assistance after that, please contact the *[Community Support|https://discord.gg/58Sxm23]*.

  • Without article:

    • helper-messages/assets/messages.yml

      Line 84 in e7264d5

      Please contact *[Mojang Support|https://help.minecraft.net/hc/en-us/requests/new]*.

    • helper-messages/assets/messages.yml

      Line 1063 in e7264d5

      Please note that this bug tracker is not for support or technical issues. If you have a payment issue or an issue with your account, please contact *[Mojang Support|https://help.minecraft.net/hc/en-us/requests/new]*. If you need help with a technical issue (i.e. Minecraft doesn't start at all), please use the *[Community Support Discord server|https://discord.gg/58Sxm23]*.

    • helper-messages/assets/messages.yml

      Line 1089 in e7264d5

      Please note that this bug tracker is not for support. If you have a payment issue or an issue with your account, please contact *[Mojang Support|https://help.minecraft.net/hc/en-us/requests/new]*.

    • helper-messages/assets/messages.yml

      Line 1111 in e7264d5

      Please contact *[Community Support|https://discord.gg/58Sxm23]* for assistance.

    • helper-messages/assets/messages.yml

      Line 1132 in e7264d5

      If there is no general outage, please first try to verify that the problem is not with your local connection or network settings. Visit *[Minecraft Community Support|https://discord.gg/58Sxm23]* for assistance.

    • helper-messages/assets/messages.yml

      Line 1135 in e7264d5

      If you are still unable to access a paid service such as a realm or purchased content, please contact [Mojang Support|https://help.minecraft.net/hc/en-us/requests/new].

• Talks about "joining the [...] Discord" while all other messages say "contact [...] support":
  

  helper-messages/assets/messages.yml

  Line 399 in e7264d5

  If that did not help, please join the *[Community Support Discord|https://discord.gg/58Sxm23]*.

• Talks about "use the [...] Discord server" while all other messages say "contact [...] support":
  

  helper-messages/assets/messages.yml

  Line 1063 in e7264d5

  Please note that this bug tracker is not for support or technical issues. If you have a payment issue or an issue with your account, please contact *[Mojang Support|https://help.minecraft.net/hc/en-us/requests/new]*. If you need help with a technical issue (i.e. Minecraft doesn't start at all), please use the *[Community Support Discord server|https://discord.gg/58Sxm23]*.

• Says "visit [...] support" instead of "contact [...] support" and calls it "Minecraft Community Support" while all other messages only call it "Community Support":
  

  helper-messages/assets/messages.yml

  Line 1132 in e7264d5

  If there is no general outage, please first try to verify that the problem is not with your local connection or network settings. Visit *[Minecraft Community Support|https://discord.gg/58Sxm23]* for assistance.

So it would probably good to:

• Consistently use or don't use an article for "support". To the native speakers, what do you think would be better?
• Consistently use "contact [...] support" (instead of "join [...]" or "visit [...]")
• Consistently call it "Community Support"

Now that #44 has been merged, the ACCESS_TOKEN secret should not be needed anymore and the person who previously created an access token (urielsalis?) can revoke it.
Effectively undoing #23.

However, before doing this, we should probably wait for the next commit on master to make sure that the changed GitHub action still works (worked on my fork at least).

E.g. WEB-2376

The Hive server no longer exists for Java Edition, thus it should probably be removed from the mji-mod message.

With 1.19.1 adding account bans soon we should probably add the banned helper message from the MCPE project to the MC project. It might also need some touchups like the Case Review Request Link: https://help.minecraft.net/hc/en-us/requests/new?ticket_form_id=360003469452

It is possible to have an extention work on mobile app (at least with Waterfox/Firefox, see uBlock Origin). It would be great to add this support for our extension too, less dependency on having a pc

The messages "Duplicate of MC-297" and "Duplicate of MC-128302" currently suggest:

However, at least for me the default is actually -Xmx2G (and not 512M). In case this is not a dynamic value depending on the available RAM, it would probably be good to update these messages. Or does someone have a different default value there?

Additionally "Minecraft: Java Edition system requirements" says that at least 4GB of RAM is required, so a maximum of 2GB for the game sounds reasonable.

The message

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

We're currently not taking bug reports for the 1.18 experiment; it is for testing the new world generation only. Please leave any new world generation-related feedback on the [feedback website|https://feedback.minecraft.net/hc/en-us/community/posts/4404932443405-Caves-Cliffs-World-Generation-Experimental-Snapshot-Feedback].

If you need help or support, you might like to follow a link below.

*Quick Links*:
📓 [Bug Tracker Guidelines|https://help.minecraft.net/hc/en-us/articles/360049840492-Mojang-Bug-Tracker-Guidelines] -- 💬 [Community Support|https://discord.gg/58Sxm23] -- 📧 [Mojang Support|https://help.minecraft.net/hc/en-us/requests/new]
📓 [Project Summary|https://bugs.mojang.com/projects/MC/summary] -- ✍️ [Feedback and Suggestions|https://feedback.minecraft.net/] -- 📖 [Game Wiki|https://minecraft.fandom.com/wiki/Minecraft_Wiki]