Template talk:Multiple issues

Template:Multiple issues is indefinitely protected from editing as it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories. Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases.

This is the talk page for discussing improvements to the Multiple issues template.

Add new text under old text. New to Wikipedia? Welcome! Learn to edit; get help. Start a new topic Assume good faith Be polite and avoid personal attacks Be welcoming to newcomers Seek dispute resolution if needed

Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15Auto-archiving period: 2 months

This template (Template:Articleissues) was considered for deletion on 2007 May 9. The result of the discussion was keep.

Please do not add the AI-generated template into this. The reason=y parameter, which people find extremely important to be visible, is not preserved when you do. Gnomingstuff (talk) 14:03, 8 May 2026 (UTC)Reply

I think it should be added. If an AI generated article has so many tags that the article needs a {{Mi}} template to collapse them, that would result in two long tags. Editors can just see the reason in the source code and, besides, I've never actually seen anyone use the |reason= parameter on that template, it's not commonly provided. FaviFake (talk) 18:06, 20 June 2026 (UTC)Reply

It didn't used to be, but now it's used pretty much all the time. Tbh I came here to see whether there was anything we could do to make the reason show in this template. Pinging @Chaotic Enby who might know a trick? Kowal2701 (talk, contribs) 14:10, 5 August 2026 (UTC)Reply

There is a way, yes. See the discussion at WT:AFDTODO § Multiple {{Merge from}} templates from different AfDs FaviFake (talk) 14:18, 5 August 2026 (UTC)Reply

There was some parallel discussion at Wikipedia:Village pump (policy)/Archive 212#c-Gnomingstuff-20260508141900-Maltazarian-20260508093100 that included some ideas on how to avoid the reason being hidden or on how to allow people who care to unhide it. Anomie⚔ 14:19, 5 August 2026 (UTC)Reply

At AfD, we're wondering whether it is possible for templates to display a different message when inside this template. For example, we would like to make the {{merge from}} template sow this when used alone:

It has been suggested that Eagle Portland be merged into this article. (Discuss) Proposed since June 2026.

And this when used inside Multiple issues:

Eagle Portland was nominated for merging into this article. (June 2026)

 You are invited to join the discussion at Wikipedia talk:Articles for deletion/Implementing the PAM–AfD merge § Multiple {{Merge from}} templates from different AfDs. FaviFake (talk) 18:14, 20 June 2026 (UTC)Reply

{{Multiple issues}} currently uses a standard orange tag. This is even the case if all the issues are yellow tags or if there is a red tag.

I'm not sure how technically feasible this is, but considering that tag colors are somewhat important (for instance a red tag signals immediate attention and is for stuff like copyright or undisclosed payments, while yellow tags are less important than orange tags and are even somewhat ignored at places like WP:ITN), I would like to suggest automatically setting the tag color of {{Multiple issues}} to the most severely-colored tag. So if its all yellow tags, set it to yellow, if there's at least one orange tag, set it to orange, and if there's at least one red tag, set it to red.

I would like to see some feedback for this idea. — Knightoftheswords 05:08, 27 July 2026 (UTC)Reply

I have no idea about the technical feasibility, but I strongly support implementing this if it is possible. Thryduulf (talk) 09:09, 27 July 2026 (UTC)Reply

Although templates like {{Orphan}}, {{POV}} and {{One source}} can look "outside" to see if they are wrapped inside a {{Multiple issues}} and so vary the message that is displayed, they are essentially black boxes - wrapper templates like {{Multiple issues}} can't look inside their contents to see what they are displaying. --Redrose64 🌹 (talk) 18:23, 27 July 2026 (UTC)Reply

Should be possible. These templates emit classes that go with their color, which a wrapping template will have access to if one uses Lua. Izno (talk) 15:56, 28 July 2026 (UTC)Reply

Same with Thryduulf, I strongly support this. EatingCarBatteries _{(contribs | talk)} 07:43, 28 July 2026 (UTC)Reply

Strongly support. Made a demo implementation at my sandbox here and the Lua for it here. Note: It won't properly display when called due to being in my userspace. I did try moving it temporarily to the module sandbox and it seemed to work properly though. FlammablePizza (talk) 17:39, 28 July 2026 (UTC)Reply

I've moved it to module space at Module:Sandbox/FlammablePizza which is the standard location so people can see it work. :) Izno (talk) 22:00, 28 July 2026 (UTC)Reply

Thanks, wasn't quite sure of the best place to keep it. The template now works properly when called. FlammablePizza (talk) 23:48, 28 July 2026 (UTC)Reply

Sounds reasonable to me. —Myceteae‍🍄‍🟫 (talk) 21:29, 28 July 2026 (UTC)Reply

I've implemented this at Template:Multiple issues/sandbox using a drastically simplified version of @FlammablePizza's script. --Ahecht (TALK
PAGE) 18:47, 30 July 2026 (UTC)Reply

Yeah, your version there is a lot more efficient. I did make a small tweak to it by making the script start from the most severe template class and returning immediately when it finds one instead of running through every template class, updating a variable each time, and returning at the end. Doesn't really matter though, given how minimal it is. FlammablePizza (talk) 19:30, 30 July 2026 (UTC)Reply

 Done. I went ahead and implemented it in the live template based on @FlammablePizza's most recent version. --Ahecht (TALK
PAGE) 13:53, 31 July 2026 (UTC)Reply