Re: Should I be reporting bugs in Pharo 3.0?
Posted by
Ben Coman on
Jul 14, 2014; 11:19am
URL: https://forum.world.st/Should-I-be-reporting-bugs-in-Pharo-3-0-tp4767284p4767681.html
Tim Mackinnon wrote:
Thanks for the fog bugz tips.
Duplicating a bug is useful for several reasons I've found in
the past:
A) if you want to submit the same bug for two streams (eg Pharo
3 & 4) to be dealt with differently - copying them is handy.
B) if you have a similar bug with similar steps bar 1, or a bug
fix improves the situation but highlights another different problem...
It's useful to duplicate a bug (with it conveniently linked) to save
time. I'm not a huge Jira fan - but it makes that really easy & I'm
suprised that fog bugz is so basic.
Of course it's not the end of the world - but you do wonder why
all bug tracking software is so clunky. I'm equally suprised that
linking bugs by using the parent/child fields is the only way - if bugs
are peers, it seems natural to just link them that way without needing
a parent.
I mentioned peers are linked by writing "Case ####", which
automatically adds the referenced case to the sidebar under "See also".
Did you mean something else? For sample see...
https://pharo.fogbugz.com/f/cases/13209/StringMorph-background
cheers -ben
Anyway - I'll use what we've got and get used to its
eccentricities.
Tim
Sent from my iPhone
On 13 Jul 2014, at 19:14, "Ben Coman [via Smalltalk]" <
[hidden email]> wrote:
Tim Mackinnon wrote:
> Can I check one more item - should I record the actual Image
version where
> bugs occur?
>
> In fogbugz, there is a version field - but I'm not sure what your
convention
> is for these things? (Is it written down somewhere for me to read
how to
> report good bugs using FogBugz).
>
> As an aside - I'm quite surprised how poor Fogbugz is. I had read
it was a
> good bug tracker - but in practice its quite minimal. I'm quite
shocked you
> can't easily duplicate a bug-report (I wrote to them and they said
you have
> to use some browser plugin as its not built in), I also can't see
how to
> link bug-report (as in, similar to X).
>
> Not Pharo's fault of course.
>
> Tim
>
There are two ways to link bug reports.
1. By writing 'Case #####' anywhere in the ticket.
2. Adding case number ##### to the Parent and Subcase fields in the
side-bar. The Pharo CI Monkey only picks up slices for a parent case
once all child cases are closed.
Now I've never needed to duplicate a bug report. I'd like to
understand
what your use case is there?
cheers -ben
To unsubscribe from Should I be reporting bugs in Pharo 3.0?,
click here.
NAML
View this message in context: Re:
Should I be reporting bugs in Pharo 3.0?
Sent from the Pharo
Smalltalk Users mailing list archive at Nabble.com.