On Tue, 2019-01-15 at 09:25 -0800, Adam Williamson wrote:
> On Tue, 2019-01-15 at 13:15 +0100, Emmanuel Seyman wrote:
> > * Jan Synacek [15/01/2019 12:45] :
> > > Unless I'm missing something, you have to use "External Trackers" on both
> > > sides. With "SeeAlso", you specified it in one bugzilla and it
> > > automatically showed in the referenced one.
> > 
> > This only works if both bugs are in the same instance. There's never been
> > inter-bugzilla-instances communication (thoough I've threatened the bugzilla
> > deps to add this).
> 
> But many of us were using it precisely *for* this. The removal seems to
> have been based on the assumption that 'See also' was *only* being used
> for referring to external bugs, but this was not in fact the case at
> all. I used it exclusively for referring to other bugs within BRC which
> were *relevant*, but not *duplicates* or *dependencies*. "External
> Trackers" does not cover this at all. To my mind they were quite
> different features.
Exactly! I don't think I've wver seen see-also pointing to an external bug,
it was always used to link related bugs in the Red Hat Bugzilla instance
& that's how I always used it as well.


> -- 
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
> _______________________________________________
> devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[email protected]
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to