Jim Hurley wrote:
Thanks Mark.
So just to clarify -- we should just put in the ascii Bug ID number
in this field (not a URL to the bug in the Sun Developer bug db)?
Indeed just the number (actually it is a text field), the field will
show a description though with a link that I directed to the Sun
Developer Bug Database and it opens with the Category set to Jini.
If you want also a link in the description that refers to the issue
directly we must enter:
Bugtraq ID [xxxxx|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=xxxxx]
I think it is a little effort and allows us to remove the custom field
one day while keeping a reference, but I consider it your call whether
we should do it.
Also I just updated all the issues that I assigned to myself or entered
recently and all current issues have a component now, but some things I
ran into:
1) all jtsk prefixed versions appeared in the unreleased part of the
multiple select list (or whatever the name is for such a thing), which
was confusing. The version should be set to released and if someone can
dig up the official release dates we can enter that information too. I
took the liberty to set the versions to 'released'. Jim are you willing
to dig up and enter the release dates. We can also archive some versions
for which we don't expect bugs to be reported after the initial upload
as that will reduce some clutter in the versions list (they won't appear
there anymore when entering issues).
2) some people fill in the fix versions field just when they resolve the
issue, others use it for scheduling purposes as well so all planned
issues show up in the roadmap and release notes reports. I'm of the
latter category and would love to do this, but it requires issue
scheduling. As we haven't done or discussed that yet I didn't fill in
the fix versions even while many of the issues are already fixed in my
workspace as I don't know in what release we are going to fix them.
Please opinions about the process we should use for 'fix version/s' field.
3) ServiceUI issues, Gregg and/or Bill ... ?
--
Mark
