Asa Dotzler [:asa] Reporter
	Description • 23 years ago

<background>b.m.o uses Bugzilla for project management tracking as well as bug
tracking. Keywords do not have the necessary relationships to be conveniently
used for many project management issues. In b.m.o, keyword traids
(keyword,keyword+ and keyword-) are used in a  nomination, approval and
rejections scheme. After a bug has been approved in the first nomination round
it becomes a nomination in the second round. There might be 2 rounds, 3 rounds
and in some cases 4 rounds of nomination and approval.  Bugzilla should be able
to recognize the relationships between the different levels and expose a new
showkeywordtree.cgi page like the dependency tree view (showdependencytree.cgi)
which shows these different hierarchy levels.

The b.m.o. idea here is that each bugzilla user could nominate that a bug be
fixed for a particular release and each developer could have a list of bugs he
wanted the OK to be working on (his own nomination plus the approval of user
nominations) and each engineering manager could have a list of bugs that he
wanted the OK for his developers to be working on (his own nominations plus the
approval of the developer nominations) and each project manager could have a
list of bugs that he wanted senior management or marketing to approve resources
for (his own nominations plus the approval of development management
nominations) and the entire pyramid should be represented in a view like a
dependency tree.

I personally favor using tracking bugs for this kind of tracking because it
pretty much works as is, but I understand that other Bugzilla consumers might
want to do this with keywords.</background>

Description of minimal request:
Bugzilla needs administrator UI to enter relationships between keywords. The
relationships can be as simple as "<keyword 1> is subordinate to <keyword 2>"
(note: <keyword 1> is not a prerequesit of <keyword 2>).  showbug.cgi should
have a "show keyword tree" link to a page where this relationship could be
displayed. This tree view would show the hierarchy below and above like
dependencies shows blocked by and blocking.

	Asa Dotzler [:asa] Reporter
	Comment 1 • 23 years ago

oops, is this a duplicate of bug 12992? I don't quite see the detail there but
it sounds like the same idea.

	Matthew Tuck [:CodeMachine]
	Comment 2 • 23 years ago

No that is about generating a dependency tree for each member of a bug list.

I have always meant to file this and thought I did, but apparently haven't.

I'm not sure "tree" is necessarily applicable all the time.  Often you want
"subkeywords" but sometimes might want mutual exclusivity instead.  So I suggest
something like this.

Ability to set up mutually exclusive keywords.  Some policy about whether
keywords automatically drop off or whether an error occurs.

Ability to set up subkeywords.  Some policy about whether an error occurs, the
subkeyword automatically gets removed when its super is added, or removed
instead since its implied.

Hmm, I remember typing this before somewhere in here ...

	Dave Miller [:justdave]
	Comment 3 • 22 years ago

Reassigning all of my "future" targetted bugs to indicate that I'm not presently
working on them, and someone else could feel free to work on them.

	Dave Miller [:justdave]
	Comment 4 • 22 years ago

Reassigning all of my "future" targetted bugs to indicate that I'm not presently
working on them, and someone else could feel free to work on them. (sorry for
the spam if you got this twice, it didn't take right the first time)

	Frédéric Buclin
	Comment 5 • 18 years ago

asa, now that we have flags, do you still want this feature?

	Asa Dotzler [:asa] Reporter
	Comment 6 • 18 years ago

no longer necessary. death to keywords!