Mailing List Archive: Trac: Users

Interpretation of ticket severity

Index | Next | Previous | View Threaded

mikael at relbe

Apr 1, 2012, 11:34 PM

Post #1 of 7 (234 views)
Permalink

Interpretation of ticket severity

I have recently realised that I may have misinterpreted the meaning of the
ticket field “severity”.

The word “severity” can be translated to Swedish in two ways, given by
context (AFAIK):

1. Degree of difficulty ("svårighetsgrad):
How hard (difficult) is it to fix this?
(Or: How bad is our life going to be trying to fix this?)

2. Degree of seriousness ("allvarlighetsgrad"):
How serious is it if we don't fix this?
(Or: How bad is our life going to be if we don't fix this?)

Until now I thought 2 applied in the context of Trac, but am starting to
think this is wrong.

How do you interpret "severity"; "difficulty" or "seriousness"?

Regards,
Mikael Relbe (mrelbe)

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

alexandrul.ct at gmail

Apr 1, 2012, 11:54 PM

Post #2 of 7 (239 views)
Permalink

Re: Interpretation of ticket severity [In reply to]

On Mon, Apr 2, 2012 at 09:34, Mikael Relbe <mikael [at] relbe> wrote:
> How do you interpret "severity"; "difficulty" or "seriousness"?

seriousness

The end user usually don't care how difficult is it to solve, it just
knows how impacted he is by the bug.

Have a nice day,
Eduard

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

trachacks at bof

Apr 2, 2012, 12:51 AM

Post #3 of 7 (230 views)
Permalink

Re: Interpretation of ticket severity [In reply to]

> The word “severity” can be translated to Swedish in two ways, given by
> context (AFAIK):
>
> 1. Degree of difficulty ("svårighetsgrad):
> How hard (difficult) is it to fix this?
> (Or: How bad is our life going to be trying to fix this?)
>
> 2. Degree of seriousness ("allvarlighetsgrad"):
> How serious is it if we don't fix this?
> (Or: How bad is our life going to be if we don't fix this?)
>
> Until now I thought 2 applied in the context of Trac, but am starting to
> think this is wrong.
>
> How do you interpret "severity"; "difficulty" or "seriousness"?

The person I inherited our trac setup from, interpreted it as
difficulty, in the sense of an estimate of the time needed to work on
the ticket. It is, however, almost never used, and I will remove / hide
it soon.

best regards
Patrick

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

trachacks at bof

Apr 2, 2012, 12:52 AM

Post #4 of 7 (233 views)
Permalink

Re: Interpretation of ticket severity [In reply to]

On Mon, 2012-04-02 at 09:51 +0200, Patrick Schaaf wrote:
> > The word “severity” can be translated to Swedish in two ways, given by
> > context (AFAIK):
> >
> > 1. Degree of difficulty ("svårighetsgrad):
> > How hard (difficult) is it to fix this?
> > (Or: How bad is our life going to be trying to fix this?)
> >
> > 2. Degree of seriousness ("allvarlighetsgrad"):
> > How serious is it if we don't fix this?
> > (Or: How bad is our life going to be if we don't fix this?)
> >
> > Until now I thought 2 applied in the context of Trac, but am starting to
> > think this is wrong.
> >
> > How do you interpret "severity"; "difficulty" or "seriousness"?
>
> The person I inherited our trac setup from, interpreted it as
> difficulty, in the sense of an estimate of the time needed to work on
> the ticket. It is, however, almost never used, and I will remove / hide
> it soon.

For the second meaning, we use priority.

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

mark.cooke at siemens

Apr 2, 2012, 1:11 AM

Post #5 of 7 (227 views)
Permalink

RE: Interpretation of ticket severity [In reply to]

> -----Original Message-----
> From: trac-users [at] googlegroups On Behalf Of Patrick Schaaf
> Sent: 02 April 2012 08:53
> To: trac-users [at] googlegroups
> Subject: Re: [Trac] Interpretation of ticket severity
>
> On Mon, 2012-04-02 at 09:51 +0200, Patrick Schaaf wrote:
> > > The word "severity" can be translated to Swedish in two
> > > ways, given by context (AFAIK):
> > >
> > > 1. Degree of difficulty ("svårighetsgrad):
> > > How hard (difficult) is it to fix this?
> > > (Or: How bad is our life going to be trying to fix this?)
> > >
> > > 2. Degree of seriousness ("allvarlighetsgrad"):
> > > How serious is it if we don't fix this?
> > > (Or: How bad is our life going to be if we don't fix this?)
> > >
> > > Until now I thought 2 applied in the context of Trac, but
> > > am starting to think this is wrong.
> > >
> > > How do you interpret "severity"; "difficulty" or "seriousness"?
> >
> > The person I inherited our trac setup from, interpreted it as
> > difficulty, in the sense of an estimate of the time needed to
> > work on the ticket. It is, however, almost never used, and I
> > will remove / hide it soon.
>
> For the second meaning, we use priority.

Personally, I think of `Severity` as (2) ~ the impact on a user of that functionality.

We use Priority as a comparative measure between all issues (e.g. in scrum this identifies the next most important tasks). The two are not necessarily directly related, a high Severity issue that is rarely used my be postponed in favour of a lower Severity issue that impacts lots of users and/or lots of the time...

~ mark c

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

rantingman at gmail

Apr 2, 2012, 1:48 AM

Post #6 of 7 (226 views)
Permalink

Re: Interpretation of ticket severity [In reply to]

On 02/04/2012, Cooke, Mark <mark.cooke [at] siemens> wrote:
> Personally, I think of `Severity` as (2) ~ the impact on a user of that
> functionality.
>
> We use Priority as a comparative measure between all issues (e.g. in scrum
> this identifies the next most important tasks). The two are not necessarily
> directly related, a high Severity issue that is rarely used my be postponed
> in favour of a lower Severity issue that impacts lots of users and/or lots
> of the time...

We use Priority for the impact on the user, and Severity as the effort
required to fix/implement.

Our local prioritisation uses a combination of the two: if we are
nearing a release, we will want to close as many low-severity tickets
as possible. If we have recently released, we will want to work on the
big tickets (both high Priority and high Severity).

CC

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

dbaldwin at playnet

Apr 2, 2012, 7:59 AM

Post #7 of 7 (227 views)
Permalink

Re: Interpretation of ticket severity [In reply to]

This is what we use as well.

Priority == when to do it (now - later - never)

Severity == how much we want it done (causes crash - must have - would
be nice - meh)

Often times I need a task done or bug fixed NOW! I can also have a task
that must be in the shipped product but I don't want it worked on until
next month.

So when making the schedule I look at severity, what's left to ship.
Developers look at priority, what are they supposed to do next.

On 4/2/2012 3:11 AM, Cooke, Mark wrote:
>> -
> Personally, I think of `Severity` as (2) ~ the impact on a user of that functionality.
>
> We use Priority as a comparative measure between all issues (e.g. in scrum this identifies the next most important tasks). The two are not necessarily directly related, a high Severity issue that is rarely used my be postponed in favour of a lower Severity issue that impacts lots of users and/or lots of the time...
>
> ~ mark c
>

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads