Nigel Daley wrote:
Perhaps the package names worked well for the engineers that originally
wrote the code and were the ones filing the bugs. In addition, the
packages for the most part delineated code ownership by engineers. I
think package names as JIRA categories have issues, however, in this new
context.
- pkg names can change
- to encourage bug filing by the largest possible
audience, I wouldn't want to assume a submitter knows
the pertinent package(s)
- a bug can cross package boundaries
- there is no code ownership, per se
And it is a list to pick your component from, that means a lot of
scrolling which ain't very user friendly.
With the custom field I told about we can also make it a list with a
fixed set of options to choose from.
However, I suspect it would be easier for the conversion process if the
old categories matched the new ones. Is that part of the reasoning with
sticking to the current categories?
Sounds reasonable. It is very easy in JIRA to 'delete' components and
have all the issues moved over to another component.
BTW and for the mentors, what are the permissions a committer has with
regard to the various JIRA 'administration' tasks?
--
Mark
