[GRASS-dev] [GRASS GIS] #561: meta: add a new "normal" bug priority

GRASS GRASS developer
1

#561: meta: add a new "normal" bug priority
-------------------------+--------------------------------------------------
Reporter: hamish | Owner: grass-dev@lists.osgeo.org
     Type: enhancement | Status: new
Priority: minor | Milestone: Website
Component: Website | Version:
Keywords: trac | Platform: Unspecified
      Cpu: Unspecified |
-------------------------+--------------------------------------------------
Hi,

could a "normal" priority be created in the trac ticket system and be set
as the default?

the default setting of "major" tends to dramatize the priority setting
into irrelevance.

thanks,
Hamish

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/561&gt;
GRASS GIS <http://grass.osgeo.org>

2

#561: meta: add a new "normal" bug priority
--------------------------+-------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: enhancement | Status: closed
  Priority: minor | Milestone: Website
Component: Website | Version:
Resolution: fixed | Keywords: trac
  Platform: Unspecified | Cpu: Unspecified
--------------------------+-------------------------------------------------
Changes (by martinl):

  * status: new => closed
  * resolution: => fixed

Comment:

Done.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/561#comment:1&gt;
GRASS GIS <http://grass.osgeo.org>

3

#561: meta: add a new "normal" bug priority
--------------------------+-------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: enhancement | Status: closed
  Priority: minor | Milestone: Website
Component: Website | Version:
Resolution: fixed | Keywords: trac
  Platform: Unspecified | Cpu: Unspecified
--------------------------+-------------------------------------------------
Comment (by hamish):

I would like to request a couple more pre-defined bug reports:

+ open tickets reported by me
+ all tickets modified in the last week

I don't know if the second one is possible, but I thought I'd ask.

Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/561#comment:2&gt;
GRASS GIS <http://grass.osgeo.org>

4

#561: meta: add a new "normal" bug priority
--------------------------+-------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: enhancement | Status: closed
  Priority: minor | Milestone: Website
Component: Website | Version:
Resolution: fixed | Keywords: trac
  Platform: Unspecified | Cpu: Unspecified
--------------------------+-------------------------------------------------
Comment (by neteler):

re "all tickets modified in the last week":

The "Active ticket" code is
{{{
SELECT p.value AS __color__,
    id AS ticket, summary, component, version, milestone, t.type AS type,
    (CASE status WHEN 'assigned' THEN owner||' *' ELSE owner END) AS owner,
    time AS created,
    changetime AS _changetime, description AS _description,
    reporter AS _reporter
   FROM ticket t
   LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority'
   WHERE status IN ('new', 'assigned', 'reopened')
   ORDER BY p.value, milestone, t.type, time
}}}

For trac admins, there is "Copy report" to clone this - then a
modification could be implemented, please suggest.

re "open tickets reported by me" - likewise.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/561#comment:3&gt;
GRASS GIS <http://grass.osgeo.org>

5

#561: meta: add a new "normal" bug priority
--------------------------+-------------------------------------------------
  Reporter: hamish | Owner: grass-dev@lists.osgeo.org
      Type: enhancement | Status: closed
  Priority: minor | Milestone: Website
Component: Website | Version:
Resolution: fixed | Keywords: trac
  Platform: Unspecified | Cpu: Unspecified
--------------------------+-------------------------------------------------
Comment (by hamish):

Replying to [comment:3 neteler]:
> re "all tickets modified in the last week":
>
> The "Active ticket" code is
{{{
  SELECT p.value AS __color__,
...
}}}
... a rather impressive bit of SQL follows ...

> re "open tickets reported by me" - likewise.

AFAIK that can be simply built with existing menus into:
http://trac.osgeo.org/grass/query?status=new&status=assigned&status=reopened&reporter=$OSGEOID

or do those reports require direct SQL into the DB?

thanks,
Hamish

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/561#comment:4&gt;
GRASS GIS <http://grass.osgeo.org>