Last modified: 2014-10-16 11:52:49 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T43197, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 41197 - Display "Mobile Platform" custom field only for relevant products/components
Display "Mobile Platform" custom field only for relevant products/components
Status: NEW
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 33158
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-19 01:36 UTC by Andre Klapper
Modified: 2014-10-16 11:52 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Andre Klapper 2012-10-19 01:36:16 UTC
I am after removing a bit of clutter from show_bug.cgi.

Mobile team prefers to keep Mobile Platform separate from Platform:
"we don't want *any* desktop os in the platform, they're useless to us. it'll be pure noise to have the desktop os list."

Hence we should show the "Mobile Platform" custom field only for products "Wikipedia App"/"Wiktionary App"/"WikiLoves Monuments Mobile" and for component "MobileFrontend".
This requires Bugzilla 4.2 as per https://bugzilla.mozilla.org/show_bug.cgi?id=479400 .
Comment 1 Andre Klapper 2012-10-26 19:37:09 UTC
Current situation and diffusion:

* "Wikimedia Mobile" is closed for new bug entries. Good.
* Several mobile apps exist, such as
  WikiLoves Monuments Mobile
  Wikipedia App
  Wiktionary App
  Commons Mobile App
* Tools/WikiSnaps exists, which is a mobile app.
* VisualEditor/Mobile should likely should also show this field.
Comment 2 Andre Klapper 2012-12-05 17:44:46 UTC
Now that we have upgraded Bugzilla to 4.2 we can define more than one product XOR product/component when a custom field (like "Mobile platform") should be shown.

Proposing to show "Mobile platform" only for:

* Commons App / General
* MediaWiki extensions / MobileFrontend
* MediaWiki extensions / MobileFrontend (Beta)
* MediaWiki extensions / ZeroRatedMobileAccess
* Tools / WikiSnaps
* WikiLoves Monuments Mobile / Browse
* WikiLoves Monuments Mobile / General
* WikiLoves Monuments Mobile / Login
* WikiLoves Monuments Mobile / Maps
* WikiLoves Monuments Mobile / Upload
* Wikimedia / WAP mobile gateway
* Wikimedia Mobile / Content
* Wikimedia Mobile / devices
* Wikimedia Mobile / Generic
* Wikimedia Mobile / Retired (Ruby) Gateway (DO NOT USE)
* Wikipedia App / Automated Builds
* Wikipedia App / Generic
* Wikipedia App / History
* Wikipedia App / Localization/Translation/Language
* Wikipedia App / Media Uploads
* Wikipedia App / Near by
* Wikipedia App / Save Article
* Wikipedia App / Search
* Wikipedia App / Settings
* Wikipedia App / Share
* Wikisource App / General
* Wiktionary App / Wiktionary
Comment 3 Andre Klapper 2013-01-11 17:07:04 UTC
Looking at this again, I wondered if there are cases apart from aforelisted components when the field is set. 
There are, especially when "Hardware" is set to "Tablet PC":
https://bugzilla.wikimedia.org/buglist.cgi?bug_id=43748,43414,43101,41984,38420,37875,38393,37160

Hence this is maybe not a good idea, and I currently think I shouldn't pursue this idea.
Comment 4 Andre Klapper 2013-01-11 17:10:02 UTC
...by the way, Bugzilla query to see which reports use the "Mobile Platform" field is https://bugzilla.wikimedia.org/query.cgi?format=advanced and setting "Custom Search" to "Mobile Platform | is not equal to | ---".
Comment 5 Andre Klapper 2014-04-22 07:48:13 UTC
Based on data how rarely this field has been set in the last 12 months (except for by the reporter and the bugwrangler), I am very tempted to just hide 
* field_label_cf_platform
* field_container_cf_platform
via "display:none" in CSS for the time being, wait if anybody will actually complain, and if nobody complains disable it entirely.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links