Template:Tracked: Difference between revisions
- العربية
- مصرى
- Azərbaycanca
- Basa Bali
- বাংলা
- Bosanski
- Català
- کوردی
- Corsu
- Čeština
- Dansk
- Deutsch
- Ελληνικά
- English
- Esperanto
- Español
- فارسی
- Suomi
- Français
- 贛語
- עברית
- Hrvatski
- Magyar
- Bahasa Indonesia
- Italiano
- 日本語
- Jawa
- Қазақша
- 한국어
- Ladin
- Latviešu
- मैथिली
- Македонски
- ဘာသာမန်
- मराठी
- မြန်မာဘာသာ
- नेपाली
- Norsk nynorsk
- Norsk
- ଓଡ଼ିଆ
- ਪੰਜਾਬੀ
- Polski
- Português
- Română
- Русский
- ᱥᱟᱱᱛᱟᱲᱤ
- Scots
- ၽႃႇသႃႇတႆး
- Simple English
- Српски / srpski
- Svenska
- தமிழ்
- ತುಳು
- తెలుగు
- ไทย
- Türkçe
- Українська
- اردو
- Oʻzbekcha / ўзбекча
- Tiếng Việt
- 中文
- 粵語
Latest revision as of 11:55, 28 November 2023
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:
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. Example with the resolved keyword:
Sample output:
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 the 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:
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.
See also
- {{Phab}}, inline link
- {{Bug}}, inline link (deprecated)
- {{Bugzilla}}, inline link (multiple items)
- {{Ptag}}, link to Phabricator projects
Link box to a bug report
| Parameter | Description | Type | Status | |
|---|---|---|---|---|
| Bug id. | 1 | Tasknumber T123 or old bugzilla number | Line | required |
| Status | 2 | For a task: open, stalled, done (or resolved), invalid, duplicate, declined, ... For a bug: critical, done (or fixed), later, wontfix (or won't fix), invalid, duplicate, ... | Line | optional |
| float | float | CSS float+clear
| Line | optional |
Editors can experiment in this template’s sandbox (edit | diff) and testcases (edit) pages.
Please add categories to the /doc subpage. Subpages of this template.