Template talk:Issue list

Issues relating to %s are maintained on the bug tracker. Report issues there.

Having the actual link piped as 'there' is not very accessible. How about being more explicit:

Issues relating to %s are maintained on the bug tracker; report issues there. View query for {{PAGENAME}}.

 Nixinova   T   C   03:56, 29 May 2024 (UTC)

It would be useful if the per-edition "And X other open issues..." be changed to link to the open issues for that edition specificlaly:

[project+=+MC+AND+resolution+is+EMPTY And 30 other open issues...]

 Nixinova   T   C   03:29, 28 June 2024 (UTC)

I also want to suggest this. In addition, when there are less issues rendered than the cutoff threshold for rendering this "and X more" sentence, I suggest to stil add the same link there but with different display text. Such as "View these on Mojira" or similar. So that the cutoff won't cut off the link. - Jack McKalling (talk) 07:22, 5 July 2024 (UTC)

To match the order pages typically use.  Nixinova   T   C   16:02, 29 June 2024 (UTC)

I've modified to module to respect the user provided order for the projects instead of using the arbitrary lua table key sort order. -- 👁 Image
MarkusRost (talk) 22:20, 2 July 2024 (UTC)

The Issues section when full takes up a significant amount of space. There are up to 25 lines of text which take up 2/3rds of the screen at a normal viewing size. I suggest limiting the results shown to < 10, and removing the "other open issues" in favor of a total issue counter combined with the version name.

Bedrock Edition - 12 open issues

• list
• list
• list

Java Edition - 14 open issues

• list
• list
• list

Mudscape (talk) 21:00, 2 July 2024 (UTC)

I think removing the other open issues would make things a bit confusing. Like, there's 14 open issues so why does this list only have 10? The other open issues answers that question as it essentially says "not everything is listed here". I'd honestly rather have both the other open issues and total open issues. I would however support (though, not very strongly) reducing the amount of issues shown, even if only by a couple, for the sake of saving a bit of space. Do you have a specific amount in mind? We could do 5 but then that feels like too little for the section to be super useful, maybe 8? - Harristic / Talk 👁 Image
21:17, 2 July 2024 (UTC)

We are already only ever showing 10 issues max. -- 👁 Image
MarkusRost (talk) 21:19, 2 July 2024 (UTC)

Even with 10 issues for both editions it's about the same length as most other sections on a page, so I'm not sure why we would want to reduce the amount of issues shown. It's a h2 section after all so there should be some content displayed in it.

However I do like the total open issues after the edition name:

Bedrock Edition – 24 open issues

Java Edition – No open issues

-- 👁 Image
MarkusRost (talk) 21:45, 2 July 2024 (UTC)

When looking at the issue list on String, I noticed that there is a mixture of issues relating to the string item, and strings of text. I tried subtracting various words from the results, such as text, words, nouns, json, etc., but there are too many unique issues relating to text strings to get them to stop showing up. This might be a unique edge case, and I'm not sure if this happens with any other blocks or items. I don't know if there's a way to modify the template so that by default, it subtracts a long list of possible words related to text strings, increasing the odds of only returning results for the string item. Are there any simple solutions I'm overlooking? Rampage455 (talk) 22:18, 30 August 2024 (UTC)

Looks like removing "word" would remove quite a few of them. Otherwise I'm not sure, this is an unfortunate negative of the new issue list. - Harristic / Talk 👁 Image
23:21, 30 August 2024 (UTC)

Can the template be modified to allow the option to show issues from only a single edition instead of both Java and Bedrock? When showing issues for a feature exclusive to one edition, sometimes the output for the other edition will be "no open issues found", and sometimes it will show a list of issues related to the search term. For an example, see the page for the Glowing effect, which is exclusive to Java, but still shows results for Bedrock. Rampage455 (talk) 13:34, 27 November 2024 (UTC)

You can already do that using |projects= which takes a comma separated list of Mojira projects. Use |projects=MC for java edition only and |projects=MCPE for bedrock edition only. -- 👁 Image
MarkusRost (talk) 13:48, 27 November 2024 (UTC)

Thanks. I guess I could have inferred that from the last example in the documentation. That should probably be listed more explicitly in the Usage section, along with a list of valid project names. I didn't even realize that bug categories for each edition were called "projects" until I took another look at the bug tracker website. I might add something to the documentation later. Rampage455 (talk) 00:09, 28 November 2024 (UTC)

I actually only added the example after your comment here, feel free to improve on it. -- 👁 Image
MarkusRost (talk) 00:11, 28 November 2024 (UTC)

The issue list no longer shows a list for me on every single page for some reason. Is this a problem on my end or a problem with the template. CrockCraftMC (talk) 16:34, 29 October 2025 (UTC)

During a recent discussion on the Discord, I saw many who do not believe this template's functionality to be worth the effort it would take to return it to functionality, especially considering the fact that the new bug tracker restricts the JQL arguments that can be used too heavily for it to be returned to how it was before the bug tracker migration, even after the recent improvements. Thus, I am opening a discussion to see whether we should properly deprecate the automated functionality of this template. 👁 Image
Sightnado ^{t | c} 14:24, 20 March 2026 (UTC)

👁 Image
 Support as proposer, I wish it were possible to have the issues list return to how it was before the migration, but that appears to be completely impossible. 👁 Image
Sightnado ^{t | c} 14:25, 20 March 2026 (UTC)

I don't want to be the one who consults the crystal ball but it might be possible that the API gets back to usable state; would it happen in the foreseeable future is, of course, a big question...

If we do agree that this system is not worth the effort, I'd argue for going the final mile and removing the template (and thus the “Issues” section) from articles altogether. Linking to the bug tracker made more sense in the times we discouraged from mentioning bugs on articles at all, but not so much now. — BabylonAS 15:35, 20 March 2026 (UTC)

Mojang is currently working on improving the search feature for the bug tracker (see here) and our use case is explicitly on the radar for future improvements. How long exactly it'll take for us to get a usable JQL search (or equivalent) I can't exactly say, but it is being actively worked on! | violine1101 ^(talk) 15:45, 20 March 2026 (UTC)