Template:Tracked/doc: Difference between revisions

Revision as of 10:36, 17 April 2015

This subpage contains documentation, categories, or other content that is not part of the template.
To view the template page itself, see Template:Tracked.

العربية ∙ asturianu ∙ Boarisch ∙ беларуская (тарашкевіца) ∙ български ∙ বাংলা ∙ català ∙ čeština ∙ dansk ∙ Deutsch ∙ Zazaki ∙ Ελληνικά ∙ English ∙ Esperanto ∙ español ∙ eesti ∙ euskara ∙ فارسی ∙ suomi ∙ français ∙ galego ∙ עברית ∙ हिन्दी ∙ hrvatski ∙ magyar ∙ Bahasa Indonesia ∙ italiano ∙ 日本語 ∙ ქართული ∙ 한국어 ∙ кыргызча ∙ Lëtzebuergesch ∙ македонски ∙ മലയാളം ∙ ဘာသာမန် ∙ Bahasa Melayu ∙ Mirandés ∙ မြန်မာဘာသာ ∙ norsk bokmål ∙ Plattdüütsch ∙ Nederlands ∙ norsk ∙ polski ∙ português ∙ português do Brasil ∙ русский ∙ sicilianu ∙ Scots ∙ slovenščina ∙ српски / srpski ∙ svenska ∙ ไทย ∙ Türkçe ∙ українська ∙ اردو ∙ oʻzbekcha / ўзбекча ∙ Tiếng Việt ∙ 中文 ∙ 中文（简体） ∙ 中文（繁體） ∙ 中文（臺灣） ∙ +/−

This template is intended to be used on feedback pages and talk pages for software deployments. It floats right-aligned next to whichever content it precedes. Imagine we see a comment like the following:

Your software is broken. It doesn't even work on Windows ME. When I try to load it, Bill Gates appears on my screen and laughs manically. --Dogmaster3000 01:17, 14 December 2011 (PST)

Now let's say we want to note that there's a task on Phabricator for this. We'll add the following code: {{tracked|T123}} (where T123 is the identifier of the task).

Sample output:

Tracked in Phabricator Task T123 Your software is broken. It doesn't even work on Windows ME. When I try to load it, Bill Gates appears on my screen and laughs manically. --Dogmaster3000 01:17, 14 December 2011 (PST)

We can leave it at that. If we'd like to note the fact that the task's been resolved, we can note its status, via {{tracked|T123|resolved}}. In addition to resolved, we support invalid, duplicate, declined, stalled and open. (Style note: We're not using big scary red colors for the status to avoid scaring or annoying the reporter.) Example with the resolved keyword:

Sample output:

Tracked in Phabricator Task T123 RESOLVED Your software is broken. It doesn't even work on Windows ME. When I try to load it, Bill Gates appears on my screen and laughs manically. --Dogmaster3000 01:17, 14 December 2011 (PST)

Of course, feel free to avoid using this template if tracking a comment is not useful.

Your software is broken. It doesn't even work on Windows ME. When I try to load it, Bill Gates appears on my screen and laughs manically. --Dogmaster3000 01:17, 14 December 2011 (PST) You appear to be running the new IE toolbar. This is expected behavior. However, if you upgrade, it will show the angry dancing Ballmer instead. --GNUnicorn 01:38, 14 December 2011 (PST)

Bugzilla tickets

For backwards compatibility, this template also accepts the number of a Bugzilla ticket as first parameter, and the following resolutions: fixed, wontfix, later, invalid. Last but not least, we can mark a bug as critical. We deliberately aren't using this keyword for bugs which are resolved one way or another -- the point of adding this to the template is to note to all readers of the page that the seriousness of a bug has been critical. This keyword should only be used if the bug has also been marked as critical in Bugzilla. Example usage: {{Tracked|300|critical}}

Sample output:

Tracked in Phabricator Task T2300 Your software is broken. It doesn't even work on Windows ME. When I try to load it, Bill Gates appears on my screen and laughs manically. --Dogmaster3000 01:17, 14 December 2011 (PST)

If you need the Phabricator task for a migrated Bugzilla ticket, add 2000 to the BZ bug number and prefix with T, e.g., T2300 replaced bugzilla:300.

Link box to a bug report

Template parameters
Parameter		Description	Type	Status
Bug id.	`1`	Tasknumber T123 or old bugzilla number	String	required
Status	`2`	resolved, stalled, invalid, ...	String	optional
float	`float`	CSS float+clear right, left, none, both, inherit Default right	String	optional

@@ Line 1: / Line 1: @@
 {{Documentation subpage}}
-<!-- Categories go at the bottom of this page and interwikis go in Wikidata. -->
-<!-- should have a "== Usage ==" section, probably? -->
-== Phabricator tickets ==
 This template is intended to be used on feedback pages and talk pages for software deployments. It floats right-aligned next to whichever content it precedes. Imagine we see a comment like the following:
@@ Line 66: / Line 61: @@
 If you need the [[phabricator:|Phabricator]] task for a migrated Bugzilla ticket, add 2000 to the BZ bug number and prefix with '''T''', e.g., [[phabricator:T2300|T2300]] replaced [[bugzilla:300]].
-<includeonly>{{#ifeq:{{SUBPAGENAME}}|sandbox||
+<includeonly>{{#ifeq:{{SUBPAGENAME}}|sandbox|<!-- NOP -->|[[Category:Maintenance templates]]
-<!-- Categories go here and interwikis go in Wikidata. -->
+[[Category:Templates using an unknown approach for internationalisation]]}}</includeonly>
-[[Category:Maintenance templates]][[Category:Templates using an unknown approach for internationalisation]]
+----
-}}</includeonly>
 <templatedata>
 {

commons>Be..anyone

Revision as of 10:36, 17 April 2015

Bugzilla tickets