Change Details

Otherwise it will be a huge mess for people to re-remember task numbers. ** Rationale ** If this issue is not fixed: * X' person-hours of work would be wasted by hundreds of frequent bugzilla users (including developers) to unlearn and re-learn issue numbers, for a cost of X dollars; * the risks that links and references to bugs break, because we're not able to redirect everything or rewrite all documents produced or printed in the last 10 years worldwide, are incalculable but probably around Y dollars; * keeping bugzilla database up for the next century to provide redirects would cost about Z dollars, when a simple apache rule would suffice if we kept the same numbers; * fixing this issue may cost W dollars. Considering 600 active users multiplied by one or more hour multiplied by average WMF hourly rate, it's clear that W << (X + Y + Z). **Resolution** Preserving Bugzilla report numbers in Phabricator is a very complex task. People used to memorize bug numbers can find the new tasks by using the old Bugzilla URLs (probably in their browser history already) or Maniphest's advanced search (see T991). Why the complexity: * We have close to 1000 tasks created in phabricator.wikimedia.org. In order to make Bug 1 T1 we would need to change the current task numbers or hack Phabricator with a local patch in order to create new series of numbers i.e. "B1". * In order to migrate 70.000 bugs in a decent time-frame (1-3 days), we need to do migrate bugs simultaneously in batches. In order to keep bug numbers, we would need to do the migration strictly sequential, starting to migrate a new bug only after the previous one has been migrated. This would increase dramatically the time required for the migration, with Phabricator and Bugzilla down. * Guaranteeing that all tasks would preserve the bug number is very risky. In the way Phabricator creates tasks via API, one error producing an incomplete attempt would create a new task that would take the next number available, breaking the correlation of bug numbers from that point. While we agree that the change of numbers will be annoying for some people with good memory, we believe that --with a bit of patience-- the problem will be solved as new numbers become as relevant as the old ones were. In the meantime, the transition should be simpler with the automatic redirects from Bugzilla URLs to Phabricator tasks, and probably even simpler when combined with the users' browser history.

Otherwise it will be a huge mess for people to re-remember task numbers. **Rationale** If this issue is not fixed: * X' person-hours of work would be wasted by hundreds of frequent bugzilla users (including developers) to unlearn and re-learn issue numbers, for a cost of X dollars; * the risks that links and references to bugs break, because we're not able to redirect everything or rewrite all documents produced or printed in the last 10 years worldwide, are incalculable but probably around Y dollars; * keeping bugzilla database up for the next century to provide redirects would cost about Z dollars, when a simple apache rule would suffice if we kept the same numbers; * fixing this issue may cost W dollars. Considering 600 active users multiplied by one or more hour multiplied by average WMF hourly rate, it's clear that W ≪ (X + Y + Z). **Resolution** Preserving Bugzilla report numbers in Phabricator is a very complex task. People used to memorize bug numbers can find the new tasks by using the old Bugzilla URLs (probably in their browser history already) or Maniphest's advanced search (see T991). Why the complexity: * We have close to 1000 tasks created in phabricator.wikimedia.org. In order to make Bug 1 T1 we would need to change the current task numbers or hack Phabricator with a local patch in order to create new series of numbers i.e. "B1". * In order to migrate 70.000 bugs in a decent time-frame (1-3 days), we need to do migrate bugs simultaneously in batches. In order to keep bug numbers, we would need to do the migration strictly sequential, starting to migrate a new bug only after the previous one has been migrated. This would increase dramatically the time required for the migration, with Phabricator and Bugzilla down. * Guaranteeing that all tasks would preserve the bug number is very risky. In the way Phabricator creates tasks via API, one error producing an incomplete attempt would create a new task that would take the next number available, breaking the correlation of bug numbers from that point. While we agree that the change of numbers will be annoying for some people with good memory, we believe that --with a bit of patience-- the problem will be solved as new numbers become as relevant as the old ones were. In the meantime, the transition should be simpler with the automatic redirects from Bugzilla URLs to Phabricator tasks, and probably even simpler when combined with the users' browser history.

Otherwise it will be a huge mess for people to re-remember task numbers. ** **Rationale **** If this issue is not fixed: * X' person-hours of work would be wasted by hundreds of frequent bugzilla users (including developers) to unlearn and re-learn issue numbers, for a cost of X dollars; * the risks that links and references to bugs break, because we're not able to redirect everything or rewrite all documents produced or printed in the last 10 years worldwide, are incalculable but probably around Y dollars; * keeping bugzilla database up for the next century to provide redirects would cost about Z dollars, when a simple apache rule would suffice if we kept the same numbers; * fixing this issue may cost W dollars. Considering 600 active users multiplied by one or more hour multiplied by average WMF hourly rate, it's clear that W <<≪ (X + Y + Z). **Resolution** Preserving Bugzilla report numbers in Phabricator is a very complex task. People used to memorize bug numbers can find the new tasks by using the old Bugzilla URLs (probably in their browser history already) or Maniphest's advanced search (see T991). Why the complexity: * We have close to 1000 tasks created in phabricator.wikimedia.org. In order to make Bug 1 T1 we would need to change the current task numbers or hack Phabricator with a local patch in order to create new series of numbers i.e. "B1". * In order to migrate 70.000 bugs in a decent time-frame (1-3 days), we need to do migrate bugs simultaneously in batches. In order to keep bug numbers, we would need to do the migration strictly sequential, starting to migrate a new bug only after the previous one has been migrated. This would increase dramatically the time required for the migration, with Phabricator and Bugzilla down. * Guaranteeing that all tasks would preserve the bug number is very risky. In the way Phabricator creates tasks via API, one error producing an incomplete attempt would create a new task that would take the next number available, breaking the correlation of bug numbers from that point. While we agree that the change of numbers will be annoying for some people with good memory, we believe that --with a bit of patience-- the problem will be solved as new numbers become as relevant as the old ones were. In the meantime, the transition should be simpler with the automatic redirects from Bugzilla URLs to Phabricator tasks, and probably even simpler when combined with the users' browser history.