Not always. I did submit a bug that was trivial (had to do with the
GTK theme). :-)
-Steven
On Tue, Aug 12, 2008 at 11:29 AM, Joachim Steiger <[EMAIL PROTECTED]> wrote:
> the problem is: for a 'user' a bug is always 'high' priority and
> 'severe', regardless what it is.
___
> On Mon, Aug 11, 2008 at 10:33 PM, Joachim Steiger <[EMAIL PROTECTED]> wrote:
>>> Is it possible to configure Trac so that only certain people (OM
>>> employees) can edit the components/milestones/severity fields?
>> in theory yes, but then i would be forced to work on loads of valid
>> request
On Mon, Aug 11, 2008 at 11:16 AM, Holger Freyther <[EMAIL PROTECTED]> wrote:
> ...
>- People playing with components, milestones, severity...
One problem I noticed that might be partially a cause of your woes
seems to be a bug in Trac. When creating a new Ticket, the default
priority and
Are you sure? Because I can no longer edit the CC field. Which is an
issue, since it seems the tickets I create don't get sent to the devel
list by default. (I assume there's something special that needs added
to make that happen).
-Steven
On Mon, Aug 11, 2008 at 10:33 PM, Joachim Steiger <[EMA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| A small example. Imagine you would be tick and responsible for
assassin. For
| some reason (probably people are unsure which component to use) people
| select "Assassin" as component and tick gets the bug m
Mike Montour wrote:
> On 11-Aug-08, at 9:16 AM, Holger Freyther wrote:
>
>> Hey,
>>
>> the signal noise ratio of the bugtracker is in a state that I'm
>> close to
>> ignoring it completely.
>>
>> It can not be that:
>> - People say +1 and me too. It is not a popularity contest
>
> The firs
On Tue, Aug 12, 2008 at 2:16 AM, Holger Freyther <[EMAIL PROTECTED]> wrote:
> Hey,
>
> the signal noise ratio of the bugtracker is in a state that I'm close to
> ignoring it completely.
>
> It can not be that:
>- People say +1 and me too. It is not a popularity contest
>- People pla
On Monday 11 August 2008 22:00:20 Olivier Berger wrote:
Hey Olivier,
> quite annoying (like the pin and keyboard ones in OM 2008.8).
Please reread the bugs. I did close both of them as WORKSFORSOME as there
never can be a real fix for all the things that were brought up. In my
WORKSFORSOME clo
Holger Freyther wrote:
> So yes as mike said we might need to educate people to not use certain fields
> (severity, milestone, component)
Remove "project management" fields like priority, severity, and milestone ?
> and to stop the too many me too's. Actually
> I think in most cases the confirm
On Monday 11 August 2008 19:23:42 Steven ** wrote:
> Is it better to leave all those fields blank then? Apparently, some
> of them have special meaning. Or is there some sort of guide/readme
> to instruct users what fields mean?
I really like mike's answer. Let us see how well that would work an
On Monday 11 August 2008 22:44:05 Andy Green wrote:
> Somebody in the thread at some point said:
> |> If things continue that way I'm _forced_ to ask our engineers to not
> |> waste
> |> their time with the bugtracker.
> |
> | If you do that, please at least hire somebody (or recruit a community
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> If things continue that way I'm _forced_ to ask our engineers to not
|> waste
|> their time with the bugtracker.
|
| If you do that, please at least hire somebody (or recruit a community
| volunteer) to go
Holger Freyther <[EMAIL PROTECTED]> writes:
> Hey,
>
> the signal noise ratio of the bugtracker is in a state that I'm close to
> ignoring it completely.
>
> It can not be that:
> - People say +1 and me too. It is not a popularity contest
> - People playing with components, milestones
On 11-Aug-08, at 9:16 AM, Holger Freyther wrote:
> Hey,
>
> the signal noise ratio of the bugtracker is in a state that I'm
> close to
> ignoring it completely.
>
> It can not be that:
> - People say +1 and me too. It is not a popularity contest
The first "me too" might be useful, confir
Is it better to leave all those fields blank then? Apparently, some
of them have special meaning. Or is there some sort of guide/readme
to instruct users what fields mean?
-Steven
On Mon, Aug 11, 2008 at 11:16 AM, Holger Freyther <[EMAIL PROTECTED]> wrote:
> Hey,
>
> the signal noise ratio of t
15 matches
Mail list logo
