Template talk:Tracked

Making the Phabricator part work

Tracked in Phabricator
Task T177

What is missing to make this template work? First real use: Phabricator/Permissions. And now here.  :)--Qgil-WMF (talk) 20:44, 17 September 2014 (UTC)

Ah, interwiki map entry requested at m:Talk:Interwiki_map#phabricator.wikimedia.org.--Qgil-WMF (talk) 22:17, 17 September 2014 (UTC)

The interwiki part is now done, and both phabricator: and phab: are enabled. The link in the template does point to valid Phabricator pages, but it looks red and it appends "?action=edit&redlink=1" to the URL.--Qgil-WMF (talk) 19:00, 24 September 2014 (UTC)

Saw the redlink, purged and now is a blue link. See this anywhere still? --Jeremyb-phone (talk) 19:37, 24 September 2014 (UTC)

First look: blue link, don't forget the Parser cache ;) --Florianschmidtwelzow (talk) 20:38, 24 September 2014 (UTC)

P.S.: The first page i saw the redlink: Phabricator/Permissions. Did a null edit, which caused a re-rendering of the page. Now there is a blue link, like expected :) Best, --Florianschmidtwelzow (talk) 11:10, 25 September 2014 (UTC)

Added mw Interwiki

Tracked in Phabricator
Task T757

Tested on commons, where no Phabricator page exists, now using mw:Phabricator. Let's see if that also works locally... –Be..anyone (talk) 01:40, 24 October 2014 (UTC)

Now also available on Meta with a /doc-subpage from commons. The /doc-subpages can be replaced by the version here when mediazilla: is closed. –Be..anyone (talk) 02:25, 24 October 2014 (UTC)

Stalled

Apparently needsinfo was replaced by stalled, cf. phab:T212, I'll try a SoFixIt. –Be..anyone (talk) 23:36, 10 November 2014 (UTC)

How to link to a Phab project workboard

{{tracked|project/board/24/}} How do we link from a project page like Frontend standards group to its Phab project workboard (phab:project/board/24/) ? It feels like another use for {{Tracked }}, but doesn't work and needs different link text. Is there a better template (we need a [Category:Phabricator templates]). -- SPage (WMF) (talk) 17:05, 11 March 2015 (UTC)

{{Tracked }} is for tasks/bugs. I think we need a separate generic template for linking to phab boards/diffusion and such. -- [[User:Edokter]] {{talk}} 20:02, 11 March 2015 (UTC)

Alignment

Suddenly this is left-aligned everywhere. Probably because template:pagelang doesn't exist? --Nemo 13:52, 23 April 2015 (UTC)

 Done. I have removed whitespaces. --Shirayuki (talk) 14:00, 23 April 2015 (UTC)

Ah, of course. Thanks! --Nemo 14:11, 23 April 2015 (UTC)

Easy to miss

On LQT boards, having the template at the right, grey on grey, doesn't exactly look nice to me (I keep ignoring it). --Elitre (WMF) (talk) 06:37, 4 May 2015 (UTC)

Hmm, that's correct, but the most visible LQT Boards will be migrated to Flow in the near future, so does this need to be fixed asap? :) --Florianschmidtwelzow (talk) 07:59, 4 May 2015 (UTC)

Yup, but what's wrong with changing now and then reverting later in case? :) --Elitre (WMF) (talk) 09:53, 4 May 2015 (UTC)

Was Flow tested for compatibility with this template? --Nemo 08:24, 4 May 2015 (UTC)

Yes, scientifically. Lonely question mark on the second line is lonely. --Elitre (WMF) (talk) 09:53, 4 May 2015 (UTC)

The versions of {{Tracked }} with 13em instead of 12em would solve the issue on your test page. I tested it with Chrome's "inspect element" feature, "edit attribute", 13 instead of 12, close div details, and at that point the question mark hopped back to where it belongs. OTOH the 13em suggestion tried to solve a Firefox issue, now we're looking at LQT and (in my case) Chrome, so I'm not sure if thats's a real "solution". Other idea(s), smaller font in the first line, and/or   instead of a space between text + (?). Another scientific result, neither 13em nor   solve the issue on the test page. –Be..anyone (talk) 13:36, 4 May 2015 (UTC)

I removed the (?) link

I Been Bold in revision 1683814 and eliminated the  (?) – if someone doesn't know what Phabricator is, the link of "Tracked in Phabricator" in the template to the Phabricator site provides a fine explanation in English and has its own link back to Phabricator/Help page. The only upside of the (?) link is it can use Special:MyLanguage to link directly to Phabricator in the reader's own language.

This also has the happy side effect of avoiding a third line in Firefox on Ubuntu, see screenshot. I earlier fixed this in revision 1416594 (make the Phabricator '(?)' help link a small superscript like edit Summary, bump width to 13em so it doesn't wrap to three lines in Firefox) , but adding space everywhere to fix one browser isn't ideal. If this sticks can someone import or merge the change to enwiki's Tracked template? Thanks. -- SPage (WMF) (talk) 01:00, 18 June 2015 (UTC)

User:FDMS4 made a similar change to commons' version yesterday ☺. The Commons version uses MyLanguage/Phabricator for the Phabricator link (I like it) and has a colon (meh). Which wiki's version is the master? -- SPage (WMF) (talk) 01:11, 18 June 2015 (UTC)

What's so meh about the colon? "Tracked in Phabricator" is not a headline of any sort. Does there have to be a master version? The Commons version was only replaced by the MediaWiki.org version for Phabricator support, from now on I guess each wiki could go its own way in terms of style choices?    FDMS  4    05:25, 18 June 2015 (UTC)

Good riddance, thanks. For a change I picked c: to update d:+m:, apparently it solves the problem reported by Elitre above. Maybe Edokter also updates w:en and other incarnations. –Be..anyone (talk) 14:09, 20 June 2015 (UTC)

I just updated en:. -- [[User:Edokter]] {{talk}} 11:43, 21 June 2015 (UTC)

Can this be tweaked?

If possible, I'd like the template to make no distinctions between "T" and "t", and ideally to accept the number, even without the letter, as a Phab ticket number, rather than a Bugzilla one. Maybe we could use a bot to replace existing instances of |XXXXXX to something like |BXXXXXX to make sure there's backwards compatibility. Thanks! --Elitre (WMF) (talk) 11:15, 15 February 2017 (UTC)

Left-floating boxes have margin on the wrong side

Tracked in Phabricator
Task T123456

This box should have a margin-right, but has a margin-left instead, which looks weird. As far as I can tell from the template source, the margin direction is currently only dependent on the page language (ltr/rtl), not on the float direction; it should probably depend on both, but I’m not strong enough in template syntax to implement it. --Lucas Werkmeister (talk) 14:25, 7 January 2019 (UTC)

This edit should fix it, though I don't think uses will reflect it until it's been marked for translation and the translation subpages have been updated. 「ディノ奴千？！」^{☎ Dinoguy1000} 14:34, 7 January 2019 (UTC)

Looks like it's live now. Thanks Shirayuki and FuzzyBot! =) 「ディノ奴千？！」^{☎ Dinoguy1000} 14:47, 7 January 2019 (UTC)

Bugzilla conversion

The bugzilla coversion (+2000 when the first parameter does not start with T) is very confusing. Since the transition is long behind us and we know the last Bugzilla ID, doesn't it make more sense to check for that value? e.g. {{#ifexpr:{{{1}}} < MAX_BUGZILLA | {{#expr:{{{1}}}+2000}} | {{{1}}} }}

I currently don't know what MAX_BUGZILLA is, but I'm sure it's not hard to find. After a bit of binary testing, it looks like MAX_BUGZILLA==73681 Strainu (talk) 20:17, 4 April 2022 (UTC)

That's just adding complexity for no real benefit. There's nothing stopping someone from referring to e.g. bugzilla:987654321, and that should be handled correctly just like any tasks with ID under MAX_BUGZILLA are. 「ディノ奴千？！」^{☎ Dinoguy1000} 01:23, 6 April 2022 (UTC)

The confusing part is that we still give preference to bugzilla, which is gone for 8+ years. Your suggestion to allow people to refer non-existent bugzilla bugs is even more so. Maybe Elitre (WMF)'s suggestion to run a bot to replace the bugzilla occurences is needed, but it's high time we move to Phabricator as default. Another option is to move the template to lua and implement the logic there, ats it would be much more readable than in Wikitext. Strainu (talk) 16:01, 6 April 2022 (UTC)

Bugzilla is only the "default" in the sense that if the number is not prefixed with "T" it's considered a Bugzilla number; however, it's completely standard to include the "T" when referring to Phabricator tasks (it's used to distinguish from other Phabricator item types, e.g. items prefixed with "P" are pastes). Whether this template should allow referring to Phabricator tasks without the prefix isn't necessarily so clear-cut, since even if all uses are updated, anyone viewing old page revisions will still run across the pre-updated Bugzilla references, which, with an updated template, will be incorrect. 「ディノ奴千？！」^{☎ Dinoguy1000} 22:05, 6 April 2022 (UTC)

Also, if prefixless numbers over the threshold would be interpreted as Phabricator tasks, it would be even more confusing, as {{tracked|300000}} would link to phab:T300000, but {{tracked|300}} would not link to phab:T300, even though that also exists. —Tacsipacsi (talk) 23:35, 6 April 2022 (UTC)

Some languages do not fit…

Hey, I’ve noticed that the main phrase “Tracked in Phabricator” translated into some languages do not fit the current width of the box, and it splits into two lines :( It appears into translations in Hindi, Nederlands, and Russian. Could be the template’s width expanded for these languages?.. — Pacha Tchernof (talk) 17:19, 24 April 2022 (UTC)