On Sat, Nov 25, 2017 at 8:20 PM, 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. > > > > Its possibly get the Bugzilla to JIRA mapping (i.e: JIRA task) using a combination of "External issue ID" and the project name, as the JIRA search string. ex: "\"External issue ID\"~2429" and project=openflowplugin -[cut]- curl -sS --header 'Accept: application/json' ' https://jira.opendaylight.org/rest/api/2/search?jql=project=yangtools%20and%20 "External%20issue%20 ID"~6972' | jq -r '.issues[].key' YANGTOOLS-694 -[/cut]- OR If you know the JIRA task already (ex: YANGTOOLS-694) we can directly search that on Jira or -[cut]- https://jira.opendaylight.org/browse/YANGTOOLS-694 -[/cut]- Thanks, Anil
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
