A partner-accessible shorten link service for buganizer issue tracker |
|
Issue descriptionWhat steps will reproduce the problem? (1) Write a b/XXXXXX link in mail (2) Ask partner to browse it What is the expected result? Redirected to https://issuetracker.google.com/XXXXXX What happens instead? Failed Currently we have crbug.com/ that will redirect to bugs.chromium.org/p/chromium, and we used to have crosbug.com/p/ that will redirect to partner issue tracker; however after the buganizer migragion, crosbug.com/p no longer works for new issues. b/ does not work for partners, which makes it harder to write short links for partners in mail. The CL changes have crosreview.com/XXX and crosreview.com/i/XXX that maps to public and internal CLs, so can we follow same convention and have crbug.com/XXX => maps to public bugs.chromium.org, and crbug.com/i/XXX => maps to old crosbug.com/p or issuetracker.google.com for larger numbers?
,
Apr 15 2017
This comes from a thread of discussion on chromeos-discuss thread. For Chrome OS, we used to have public issues on http://code.google.com/p/chromium-os private issues on http://code.google.com/p/chrome-os-partner And due to the shutdown of code.google.com, bugs have been migrated to public issue on https://bugs.chromium.org/p/chromium/issues/list private issues on buganizer That's why we want to migrate an change short links. |
|
►
Sign in to add a comment |
|
Comment 1 by s...@google.com
, Apr 15 2017