Template:Tracked/doc

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:

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

Sample output:

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. In addition to, we support  ,  ,  ,   and. (Style note: We're not using big scary red colors for the status to avoid scaring or annoying the reporter.) Example with the  keyword:

Sample output:

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

Bugzilla tickets
For backwards compatibility, this template also accepts the number of a Bugzilla ticket as first parameter, and the following resolutions:,  ,  ,. 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:

Sample output:

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 300.

{	"description": "Link box to a bug report", "params": { "1": {			"label": "Bug id.", "description": "Tasknumber T123 or old bugzilla number", "type": "string", "required": true },		"2": {			"label": "Status", "description": "resolved, stalled, invalid, ...", "type": "string" },		"float": { "description": "CSS float+clear right, left, none, both, inherit", "type": "string", "default": "right" }	} }