Template talk:Issue list

Template doesn't work
This template does not work, right? iLeon 15:00, 17 March 2013 (UTC)


 * The template works fine. It's JIRA's API which doesn't, so the issue list isn't embedded into the page; but that's fine, the issues can still be viewed by clicking the link. –ultradude25 ᐸ Talk Contribs 15:10, 17 March 2013 (UTC)


 * So bugs are not listed on some page? iLeon 15:13, 17 March 2013 (UTC)


 * Bugs are not shown on any page until JIRA has CORS support. –ultradude25 ᐸ Talk Contribs 15:14, 17 March 2013 (UTC)


 * Ok, thanks! iLeon 15:40, 17 March 2013 (UTC)


 * It just shows an empty space when clicking expand. -- Number  maniac  (C)  23:58, 23 March 2013 (UTC)

Until the API is fixed, perhaps the template should be modified to display something more explicitly helpful? "Issues related to are maintained at LINK. Report new issues at LINK." or something? &mdash;Munin295 &middot;  &middot; 21:36, 29 March 2013 (UTC)


 * It does already give the bug tracker link. That might be a good idea though. Ultra dude, what do you think? -- Numbermaniac  - Talk  (C)  23:55, 29 March 2013 (UTC)


 * I've changed the wording a bit, commented out the collapsible table and made it so the "related to" part lists all the search terms. –ultradude25 ᐸ Talk Contribs 03:06, 30 March 2013 (UTC)


 * Works perfect, except that it leaves about 3 lines of space underneath. Nothing major though. -- Numbermaniac  - T  - C 10:32, 30 March 2013 (UTC)


 * I can't really do anything about that because that's the space where the issue list world go, if it were working. –ultradude25 ᐸ Talk Contribs 06:21, 31 March 2013 (UTC)


 * That's alright. Thanks anyway. -- Numbermaniac  - T  - C 07:10, 31 March 2013 (UTC)

Doesn't work with multiple issues?
When I add search terms to the template call, it doesn't show just unresolved.... It shows everything. -- (T)  Numbermaniac  (C)  00:39, 24 March 2013 (UTC)


 * . –ultradude25 ᐸ Talk Contribs 00:57, 24 March 2013 (UTC)


 * Wow, that was quick. Thanks! -- (T)  Numbermaniac  (C)  01:15, 24 March 2013 (UTC)

JIRA and manual bug display on pages
As discussed on ultradude25's talk page, and above on this page, JIRA's API is currently not working. I would suggest not manually placing bugs on pages, which defeats the purpose of this template in the first place. It's really not that much of an issue to click the issue tracker link while treating the expand/collapse function as a neat addition. The reason manually adding bugs defeats the purpose is that doing so invites users to start throwing in their bugs and not reporting them to the tracker, among other issues with the old bugs sections, like not keeping up with new ones and having old ones sit there. I'm only making this as a suggestion and not really requesting consensus on it, but just wanted to point out the past pitfalls of maintaining a manual bug list. 03:17, 24 March 2013 (UTC)


 * Sorry. It's just that people reported bugs on Ocelot commonly, so I thought that I should place the bugs there to prevent people adding further bugs in the list. -- (T)  Numbermaniac  (C)  04:21, 24 March 2013 (UTC)


 * Nothing wrong with what you were doing, I was just voicing my thoughts on the matter. Having the bug link templates there could also deter bug reporting to an extent. Personally, I just revert it, but I tend to be a little harsh with removing stuff that doesn't belong.  04:47, 24 March 2013 (UTC)

Whitespace
This template causes unnecessary line breaks beneath it that have bugged me since I started using this wiki :) I just tried getting rid of them by commenting out a line break (one of the breaks that were part of the deactivated table code), but that didn't work. In my tests, removing the  works (near the end of the code, the only thing that's within the body of the  ). I'm hesitant to remove it without knowing why it's there. Is there any need for it?  Equazcion  ( talk )  18:18, 10 Jun 2013 (UTC)
 * After testing and digging around, I've concluded the  is likely unnecessary, so I removed it. The whitespace is now gone. If that   was meant to serve some purpose in displaying the issues lists, that can be addressed if/when the API for that feature ever starts working.  Equazcion  ( talk )  20:58, 10 Jun 2013 (UTC)


 * It's required to stop HTMLTidy deleting the empty element, by making it not empty. –ultradude25 ᐸ Talk Contribs 00:01, 11 June 2013 (UTC)


 * Ok. I'm guessing no one has any idea why an nbsp would be causing so much whitespace, or it's a stylesheet thing? PS. Why remove mention in the documentation that the issues list isn't currently functioning?  Equazcion ( talk )  00:22, 11 Jun 2013 (UTC)


 * Because it's in a div so it gets its own line. That was incorrect, it works, the issue list just isn't transcluded into the page. –ultradude25 ᐸ Talk Contribs 00:26, 11 June 2013 (UTC)


 * I know, that's why the notice I had added said "due to a backend issue". Either way, can we add something you'd be more comfortable with to note that the issues list won't be showing up, so as not to frustrate people who can't seem to get it to work? On the div thing, I figured that, but when I tried display:inline that didn't get rid of the whitespace.  Equazcion  ( talk )  00:30, 11 Jun 2013 (UTC)


 * You said entering parameters wouldn't have any effect, which is wrong, the link is still there. The line above it is a paragraph, which also gets its own line. –ultradude25 ᐸ Talk Contribs 01:12, 11 June 2013 (UTC)


 * Alright, so can we re-add the notice, without mention of parameters not working? If "inline" is set on the div, it should become part of the previous paragraph (the previous paragraph being the line that is actually displayed), without creating new lines of whitespace. Unless I'm missing something here.  Equazcion ( talk )  01:20, 11 Jun 2013 (UTC)


 * I don't see it being worth mentioning really, just remove the bit that says it shows them on the page. That was just a bonus on the original template anyway.
 * Paragraphs are block elements just like divs. It doesn't matter what you set the div to, it's still not in the paragraph, so gets forced on a separate line. I don't want to remove the div, because then when Atlassian finally get their shit together, it will work straight away, and we'll know they fixed it. –ultradude25 ᐸ Talk Contribs 02:28, 11 June 2013 (UTC)
 * Alright regarding the div. I'm sure there must be a way to remove the whitespace without removing the div, but I'm not sure how yet. As for the notice though, since 95% of the documentation describes features that won't currently work, why not put up a notice so that people know this?  Equazcion ( talk )  02:33, 11 Jun 2013 (UTC)
 * Okay I think I got it. If we enclose the displayed line in a div with display:inline, and add display:inline to the issues div, the whitespace is gone. See User:Equazcion/e and let me know what you think.  Equazcion ( talk )  02:46, 11 Jun 2013 (UTC)


 * Everything the documentation describes works and is usable.
 * That won't work. When the API is finally fixed, it will mean the issue list shows up on the same line as the text. –ultradude25 ᐸ <small style=display:inline-block;line-height:1em;vertical-align:-.4em>Talk Contribs 03:16, 11 June 2013 (UTC)
 * The documentation seems to indicate that it will be "displaying 20 results" by default, but it actually just displays a link, and no issues are displayed til you click it. Put it this way: The documentation was written for the template's use as a displayer of issues, and currently it doesn't do that; it displays a link instead. It doesn't currently work as people reading this documentation would reasonably expect it to. Can we clarify this somehow? <font face="Century Gothic" style="text-shadow:1px 1px 3px #999;"> Equazcion ( talk )  03:34, 11 Jun 2013 (UTC)


 * Commented out those parts. –ultradude25 ᐸ <small style=display:inline-block;line-height:1em;vertical-align:-.4em>Talk Contribs 03:54, 11 June 2013 (UTC)

Great, thanks :) However... is there any particular reason for the resistance to a notice as well? The template name itself seems to indicate that a list will be displayed. Otherwise it would be called "issues link". I'm thinking a notice like, "This does not currently list issues, but provides a link to the issue list" would seem to clarify things. <font face="Century Gothic" style="text-shadow:1px 1px 3px #999;"> Equazcion ( talk )  04:02, 11 Jun 2013 (UTC)


 * Done. –ultradude25 ᐸ <small style=display:inline-block;line-height:1em;vertical-align:-.4em>Talk Contribs 04:16, 11 June 2013 (UTC)


 * Awesome, thanks :) <font face="Century Gothic" style="text-shadow:1px 1px 3px #999;"> Equazcion ( talk )  04:18, 11 Jun 2013 (UTC)

Default setting
Can the default be switched from to  ? It would allow much better use for Biome/Desert and others like it, especially since Biome/Desert is a minecraft wiki name. --<b style=color:#048>KnightMiner</b> ( talk 16:29, 20 May 2014 (UTC)


 * Those pages shouldn't really exist anyway, and certainly shouldn't be subpages of biome. –Matt ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px>Talk Contribs ⎜ 03:17, 21 May 2014 (UTC)

Are "Invalid" issues really needed?
It seems that issues with resolution "Invalid" (resolution 7) are included in the issue list. However, Invalid issues are usually issues that are due to incorrect commands/typos, feature requests (instead of bug reports), technical support issues, outdated Java, mod usage, and the like. So, since they usually don't contain substance (relating to the article), are they really needed?

Also the arguments ("and","or", "order by" etc) in the filter are lowercase instead of uppercase (AND), which is how JIRA typically puts it.

Also unrelated, but is JIRA's API still broken? - Sonicwave talk  09:12, 17 November 2014 (UTC)


 * Between "Won't fix" and "Works as intended", all potential actual issues that are closed without action are covered. It really does not benefit too much to the user finding actual issues. –<font color=#048>KnightMiner  (t 15:43, 17 November 2014 (UTC)


 * I have removed the "Invalid" resolution from the template (capitalization arguments not changed); loading up the issues on Sword and Flint and Steel caused no issues. If anyone disagrees with this change (or if it broke something), feel free to revert or discuss here. - Sonicwave talk  05:41, 18 November 2014 (UTC)


 * After further testing it seems to work just fine :). - Sonicwave talk  06:44, 18 November 2014 (UTC)