On Wed, 4 Mar 2009, James Carlson wrote:
timeless writes:
I'm not sure I understand that one. Either a bug is being cloaked
because it's security sensitive or it's not.
Why would there be two flags?
The first flag is the generic one. The second one is the real
underlying flag, I see it b
On Tue, 3 Mar 2009, James Carlson wrote:
Valerie Bubb Fenwick writes:
We am looking at things that are missing from bugzilla
that would hold us back from using this as the sole
bugtracking tool for Solaris/OpenSolaris, instead of
the two we are using now.
In addition to Danek's fairly complet
On Thu, Mar 5, 2009 at 1:36 AM, Danek Duvall wrote:
>> Nice to have
>
> - A scalability issue -- we have a version for each build. For now,
> that's fine, but if this continues for one release after another, the
> scroll box is going to get unwieldy. In bugster, we've got essentially
>
On Wed, Mar 04, 2009 at 05:47:50PM -0800, Max Kanat-Alexander wrote:
> On Wed, 4 Mar 2009 15:38:45 -0800 Danek Duvall
> wrote:
> > Hm. Free text fields are definitely not okay,
>
> You can add custom select fields, too.
Yup. Thing is, its data needs to draw from the same pool as the pro
On Wed, 4 Mar 2009 10:13:31 -0500 James Carlson
wrote:
> That doesn't sound quite right to me. When a real security bug is
> filed, the *submitter* must mark it that way, even if the submitter is
> not part of the special group.
Yes, Bugzilla does actually support that.
> More generall
On Wed, 4 Mar 2009 15:38:45 -0800 Danek Duvall
wrote:
> Hm. Free text fields are definitely not okay,
You can add custom select fields, too.
> and I'm not aware of a
> way to require a "resolved in version" field to be filled in when
> changing state, only that a comment is required.
On Wed, Mar 04, 2009 at 01:36:30AM -0800, Hugh McIntyre wrote:
> This must be a setup issue. Since the Bugzilla installation I use at
> work very definitely has "Found in release version" and "Resolved in
> release version" fields. These are free-text fields rather than a
> pre-defined list, whi
Another dribble.
> Nice to have
- A scalability issue -- we have a version for each build. For now,
that's fine, but if this continues for one release after another, the
scroll box is going to get unwieldy. In bugster, we've got essentially
two levels -- release and build.
Danek
timeless writes:
> > I'm not sure I understand that one. Either a bug is being cloaked
> > because it's security sensitive or it's not.
>
> > Why would there be two flags?
>
> The first flag is the generic one. The second one is the real
> underlying flag, I see it because i'm in the group. You
On Wed, Mar 4, 2009 at 5:13 PM, James Carlson wrote:
> That doesn't sound quite right to me. When a real security bug is
> filed, the *submitter* must mark it that way, even if the submitter is
> not part of the special group. If it doesn't work that way, then
> security bugs will "leak," and th
timeless writes:
> James Carlson wrote:
> > I've looked, and I don't see anything like that in the user interface.
> > Perhaps I haven't looked in the right places, though, or maybe it's
> > just that our version is too old. I don't see anything related to
> > "security."
>
> When Alan writes tha
On Wed, Mar 04, 2009 at 01:48:34AM -0800, Hugh McIntyre wrote:
> I realize this is a personal preference, but this one seems survivable.
Of course it is; that's why it's merely "nice to have". I just hate
wasting the vertical space on every browser window with a bookmarks
toolbar. It's the fi
James Carlson wrote:
> I've looked, and I don't see anything like that in the user interface.
> Perhaps I haven't looked in the right places, though, or maybe it's
> just that our version is too old. I don't see anything related to
> "security."
When Alan writes that it isn't set up, he means it
On Wed, 04 Mar 2009 01:48:34 -0800 Hugh McIntyre
wrote:
> (adding attachments when filing a
> bug in the first place would be the most helpful to me personally),
You can do that.
-Max
--
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything
Danek Duvall wrote:
Very nice to have / painful to live without
- You can't add an attachment and make other changes to a bug in the same
transaction (other than adding a comment).
While this is certainly irritating (adding attachments when filing a bug
in the first place would be the m
Danek Duvall wrote:
On Mon, Mar 02, 2009 at 05:12:16PM -0800, Danek Duvall wrote:
Very nice to have / painful to live without
- There's no way to associate bug state with a particular build. There's
"target milestone", which sort of corresponds to "commit to fix in
build", but ther
On Mon, Mar 02, 2009 at 05:12:16PM -0800, Danek Duvall wrote:
> Very nice to have / painful to live without
- There's no way to associate bug state with a particular build. There's
"target milestone", which sort of corresponds to "commit to fix in
build", but there's no "fixed in build
Hi,
in case somebody is interested what we did in OpenOffice.org:
before having also IssueTracker (an stone age old derivate of bugzilla,
formerly also know as IssueZilla) on the OpenOffice.org site, we already
dealt with two different bug tracking systems, the old StarOffice
(StarDivision) o
Alan Coopersmith writes:
> James Carlson wrote:
> > Valerie Bubb Fenwick writes:
> >> We am looking at things that are missing from bugzilla
> >> that would hold us back from using this as the sole
> >> bugtracking tool for Solaris/OpenSolaris, instead of
> >> the two we are using now.
> >
> > In
Max Kanat-Alexander writes:
> On Tue, 3 Mar 2009 10:28:51 -0500 James Carlson
> wrote:
> > We use that "security" flag to bowdlerize bug reports. Bugzilla
> > seems to have no equivalent.
>
> You can protect a bug from being viewed using Bugzilla's
> security groups. You cannot hid
James Carlson wrote:
> Valerie Bubb Fenwick writes:
>> We am looking at things that are missing from bugzilla
>> that would hold us back from using this as the sole
>> bugtracking tool for Solaris/OpenSolaris, instead of
>> the two we are using now.
>
> In addition to Danek's fairly complete compa
Milan Jurik writes:
> I heard that Al Ikner is involved in this process and he is working on
> other (not so relevant here) changes in escalation process. So I would
> recomend to speak with him.
Not "me," I hope. I was answering Valerie's call for a list of known
gaps, not volunteering to drive
On Tue, 3 Mar 2009 10:28:51 -0500 James Carlson
wrote:
> We use that "security" flag to bowdlerize bug reports. Bugzilla
> seems to have no equivalent.
You can protect a bug from being viewed using Bugzilla's
security groups. You cannot hide individual fields, but you can hide
in
Milan Jurik wrote:
Hi James,
V út, 03. 03. 2009 v 17:01, James Carlson píše:
Milan Jurik writes:
Hi James,
V ,Az(Bt, 03. 03. 2009 v 16:28, James Carlson p,Am$,1!!(Be:
[...]
one. (One fix, which would work for Bugster as well, would be to
demand that RPE engineers working on a
Danek Duvall writes:
> On Tue, Mar 03, 2009 at 10:28:51AM -0500, James Carlson wrote:
>
> > "Can't Live Without"
> >
> > General access to keywords. As it stands, you have to have some
> > sort of special administrative access in Bugzilla to create
> > keywords. I'm able to create
Hi James,
V út, 03. 03. 2009 v 17:01, James Carlson píše:
> Milan Jurik writes:
> > Hi James,
> >
> > V ,Az(Bt, 03. 03. 2009 v 16:28, James Carlson p,Am$,1!!(Be:
> > [...]
> > > one. (One fix, which would work for Bugster as well, would be to
> > > demand that RPE engineers working
Milan Jurik writes:
> Hi James,
>
> V ___
tools-discuss mailing list
tools-discuss@opensolaris.org
On Tue, Mar 03, 2009 at 10:28:51AM -0500, James Carlson wrote:
> "Can't Live Without"
>
> General access to keywords. As it stands, you have to have some
> sort of special administrative access in Bugzilla to create
> keywords. I'm able to create user accounts, products, and flags
Hi James,
V út, 03. 03. 2009 v 16:28, James Carlson píše:
[...]
> one. (One fix, which would work for Bugster as well, would be to
> demand that RPE engineers working on an escalation set the RE
> field to themselves.)
We (Solaris RPE) are assigning as RE ourselves even today. At lea
Valerie Bubb Fenwick writes:
> We am looking at things that are missing from bugzilla
> that would hold us back from using this as the sole
> bugtracking tool for Solaris/OpenSolaris, instead of
> the two we are using now.
In addition to Danek's fairly complete comparison (and I agree that
treatin
On Mon, Mar 02, 2009 at 07:09:32PM -0800, Max Kanat-Alexander wrote:
> On Mon, 2 Mar 2009 17:12:16 -0800 Danek Duvall wrote:
> > - When selecting components within a product, there's no immediately
> > available description for each one
>
> When you're filing a bug, there is, unless
On Mon, 2 Mar 2009 17:12:16 -0800 Danek Duvall
wrote:
> - When selecting components within a product, there's no immediately
> available description for each one
When you're filing a bug, there is, unless you've customized it
out or aren't on a new-enough 3.2 release to have it.
>
Very nice to have / painful to live without
- While at the current level, interest lists are a "nice to have", if
we're going to move to bugzilla for everything, we really do need a
more scalable solution. Having to go in and create a watcher alias for
every single component is tedi
Hi gang -
We're trying to help the defect tracking team with
a Gap Analysis between bugzilla and bugster. We realize
this is an external alias, so many of you will not have
access to bugster, but we thought this would also be a
good way to reach the Sun internal folks who have
bugster experience
34 matches
Mail list logo
