crossreference components




16 years ago
7 years ago


(Reporter: Brant Gurganus, Unassigned)


(Depends on: 1 bug)




16 years ago
Bugs in databases while in one component can be crossreferenced to other
components.  For example: evangelism > documentation would be a crossreference
for documentation > developer.
I'm not sure what you mean. You want the components to be identical?

Comment 2

16 years ago
Currently, there could be multiple paths to a component just like there are
multiple paths to a website in a search engine such as  Search engines
solve this problem by crossreferencing from say computers > internet > WWW >
editors to computers > software > editors > HTML.  I would like to see the same
possibility in Bugzilla.  If it is already there I haven't seen it used.

Comment 3

16 years ago
Hmm yeah, why not. This could come in handy in certain situations where you have
common components between projects. 
Severity: normal → enhancement

Comment 4

16 years ago
It might also be useful to create a Bugzilla API that could allow Bugzilla to
send reports to other Bugzillas.  For example if I went to Caledar > libical
then it would actually file the bug in, if they used it, Bugzilla for the
external libical component

Comment 5

16 years ago
See also bug 43940, "Component trees".


16 years ago
Depends on: 43940
Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.
Assignee: justdave → general
QA Contact: mattyt-bugzilla → default-qa
Duplicate of this bug: 644634


7 years ago
Duplicate of this bug: 644634
You need to log in before you can comment on or make changes to this bug.