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)

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)