Difference between revisions of "Template talk:Issue/Version 1"
(Some examples?) |
|||
Line 2: | Line 2: | ||
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.<br/>-- '''[[User:Haravikk_Mistral|Haravikk]]''' <sup><small>([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]])</small></sup> 08:09, 20 April 2011 (PDT) | 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.<br/>-- '''[[User:Haravikk_Mistral|Haravikk]]''' <sup><small>([[User_talk:Haravikk_Mistral|talk]]|[[Special:Contributions/Haravikk_Mistral|contribs]])</small></sup> 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. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 10:53, 20 April 2011 (PDT) | |||
{{{!}} | |||
{{Issue|VWR-123|OpenJPEG meta decode, Second Life patches|resolution=fixed|type=bug}} | |||
{{Issue|VWR-234|Incorrect notice on land buy floater|resolution=fixed|type=bug}} | |||
{{!}}} |
Revision as of 09:53, 20 April 2011
Some examples?
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 |