Template talk:Issue/Version 1
I think this page could do with some example uses of the template, as I've tried several times to use it assuming it would be identical to Template:Issues, however it never seems to work properly (possibly a bug?) while Issues works fine, barring of course the necessity of adding an IssueTable which is overkill for single items.
-- Haravikk (talk|contribs) 08:09, 20 April 2011 (PDT)
In principal Issue should not be used directly at all. The description of issues should be easy to pull into any article and in a perfect world would be pulled directly from JIRA but barring world perfection, defined on the wiki once. The setup cost is annoying but in the long run it keeps other people from having to pay the same setup cost and makes all instances easy to update.
I can guess why you want to use it, so you can catalog your bugs. For that purpose it doesn't make sense to have to pay the setup cost for each bug, especially if there is little reuse interest. I'll take a look into Issue and see what can be done to make this usecase less painful.
The reason for the complexity is how issues are used in the LSL articles. One section for important issues (bugs), another for all issues. This requires both content duplication (non-linear editing) and content awareness; all in a language that does not have arrays or lists. Most of this awareness is placed in the Issues template but some is in Issue. Considering the Jira updates in the last year, it's time to revisit the templates feature set. -- Strife (talk|contribs) 10:53, 20 April 2011 (PDT)
|VWR-123||OpenJPEG meta decode, Second Life patches|
|VWR-234||Incorrect notice on land buy floater|
- Oh I do know how to use it I think, it's just that the page itself has no examples to show correct usage of either it, or the Template:Issues template, which I think would be good to have, at least so people understand them better. In my particular case I was hoping to use the format of Template:Issue in a list for adding JIRA issues to office hour agendas, but that was asking for all kinds of trouble it seems. I'm wondering, how easy would it be to create a template that can use the contents of Template:Issues to create a JIRA issue for inclusion outside of a table, i.e - without cell data? It just seems like there might be a good level abstraction somewhere so we can use the same format for all JIRA issue declarations, and then templates that can take them and turn them into an inline or table-row format, so that all JIRA issue declarations can use the same basic format, same parameters etc., but be used all over the place, either being declared on the page as you've done in your example above, or as their own wiki sub-page, and then be used anywhere.
- Most of my own stuff that I've been adding as Issues sub-pages I've been doing so I can add them to relevant functions in the LSL portal so people can see existing JIRA issues to solve known problems. But it seems like there must be a way to make the format usable for rich JIRA references in more places.
-- Haravikk (talk|contribs) 03:30, 21 April 2011 (PDT)
I noticed this template has been updated to note that it's being phased out, but I don't see a link to the new template? Is it one of the Jira templates?
-- Haravikk (talk|contribs) 03:51, 27 September 2013 (PDT)
- Yeah I haven't written it yet but I know I won't come back and rewrite the documentation after I've written the new template so I thought I'd write it now. There aren't many places where Template:Issue is used directly so to keep all the Template:Issues's working, it will detect which template should be used. I haven't decided yet if I'm going to keep the root a redirect to the new version or just write it in the root. The main goal is to streamline usage for BUG which is greatly simplified and to add "fix info". -- Strife (talk|contribs) 21:37, 27 September 2013 (PDT)