Look for the externalid field in jira. It has the bugzilla id. Create a search filter and save it.
Andy is also working on getting the links in gerrits to go to the jira issues same as we had for bugzillas. Until then we paste the full jira url in the commit message. On Nov 25, 2017 5:21 AM, "Claudio David Gasparini" <[email protected]> wrote: Hi All, I have a wonder regarding this migration. We usually use to check the BUG on the header of the commit to link the bung under Bugzilla and therefore have a access for the full details of the issue. Since this migration, If I try to find some historical, I have to go to BZ, copy some text under it and search in Jira. This is ugly but working so far, but once BZ is gone, there wont be any way to have access to the historical, or I will have to go bug by bug in Jira, since there is no mention on any new bug created in Jira from which BZ bug is coming from. In conclusion, Is there some step in plan to be solve this. Or I'm just missing something, maybe some other way to find the relation bugzilla bug <->Jira bug. Any tips will be great. Thanks and regards, Claudio ------------------------------ *From:* Andrew Grimberg <[email protected]> *Sent:* Monday, October 30, 2017 10:49:49 PM *To:* Michael Vorburger *Cc:* OpenDaylight Dev; <[email protected]>; IT Infrastructure Alerts; release ([email protected]); OpenDaylight Discuss *Subject:* Re: [release] [opendaylight-dev] ODL Bugzilla to JIRA migration 2017-10-18 @ 12:00 - 15:30 PDT (19:00 - 22:30 UTC) On 10/23/2017 03:24 AM, Michael Vorburger wrote: > On Wed, Oct 18, 2017 at 11:59 PM, Andrew Grimberg > <[email protected] <mailto:[email protected] <[email protected]>>> > wrote: > > What is the timeline on this point, the actual bugs.opendaylight.org > <http://bugs.opendaylight.org> sunset / shutdown? Days, weeks, months? A few months at most before it's shutdown for good. The system that it currently resides on is scheduled for termination after other services get moved off of it before the end of the year as we re-arrange hosting. > If it's not too much of a bother for you and not a cost issue (shouldn't > be), then IMHO there would be value in keeping BZ up (as read-only) for > a while.. ike maybe 6 months or so? Various e.g. list posts et al > (Google search results) have links to bugs.opendaylight.org > <http://bugs.opendaylight.org> and it would be "nice" for those to keep > working for a while. > Also, once it does have to go, perhaps you could have a HTTP redirect > at bugs.opendaylight.org/* <http://bugs.opendaylight.org/*> > to jira.opendaylight.org <http://jira.opendaylight.org>, to avoid future > confusion? Yes, we'll be redirecting eventually. -Andy- -- Andrew J Grimberg Lead, IT Release Engineering The Linux Foundation _______________________________________________ release mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/release
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
