Difference between revisions of "Template:Issues"
Jump to navigation
Jump to search
(lighten the load this should) |
m |
||
| Line 1: | Line 1: | ||
<includeonly>{{#vardefine:issues|{{#var:issues}} | {{Template|{{#ifeq:{{NAMESPACE}}|Template|Multi-lang}}}}<includeonly>{{#vardefine:issues|{{#var:issues}} | ||
{{Issue|{{{1}}}|{{{2|}}} | {{Issue|{{{1}}}|{{{2|}}} | ||
|style={{{style|}}} | |style={{{style|}}} | ||
| Line 11: | Line 11: | ||
This template has the exact same parameters as [[Template:Issue]] but instead of returning the table entry it puts it in a variable that can be accessed by [[Template:IssueTable]] or any of the LSL Templates. This allows for a more free form page layout and the templatization of jira issues. The advantage of which is that the data that makes up an issue need not be placed on all articles, just the template. | This template has the exact same parameters as [[Template:Issue]] but instead of returning the table entry it puts it in a variable that can be accessed by [[Template:IssueTable]] or any of the LSL Templates. This allows for a more free form page layout and the templatization of jira issues. The advantage of which is that the data that makes up an issue need not be placed on all articles, just the template. | ||
For a list of templatized issues see: [[:Category:Jira Issues]]</noinclude> | For a list of templatized issues see: [[:Category:Jira Issues{{#var:lang}}]]</noinclude> | ||
Revision as of 13:38, 10 December 2008
{{Multi-lang}} This template has the exact same parameters as Template:Issue but instead of returning the table entry it puts it in a variable that can be accessed by Template:IssueTable or any of the LSL Templates. This allows for a more free form page layout and the templatization of jira issues. The advantage of which is that the data that makes up an issue need not be placed on all articles, just the template.
For a list of templatized issues see: Category:Jira Issues