ထႅမ်းပလဵတ်ႉ:Tracked
ၶေႃႈၽၢင်ႉ တႃႈ ၽူႈမႄးထတ်းၶဝ် - Please don't categorize this template by editing it directly. Instead, place the category in its documentation page, in its "includeonly" section.
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:
|
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. (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:
|
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)
|
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:
|
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
မႄးထတ်း- mw:Template:Phabricator - similar to
[[phab:n]] - mw:Template:PhabT - similar to
[[phab:n]]but without the "T" - mw:Template:Ptag - page-top indicators for overall #projects and #tags
Link box to a bug report
| Parameter | ၶေႃႈသပ်းလႅင်း | 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
| String | optional |