Opened 6 years ago

Closed 6 years ago

#1729 closed volunteer task (wontfix)

Trac Clean Up

Reported by: TimLoal Owned by: TimLoal
Priority: minor Milestone: unassigned
Component: Trac Keywords:
Cc:

Description

I Just had a good clean up on trac. Closed ~80 tickets 25%, moved all tickets from the 'unknown' type and the 'unassigned' component and moved as many tickets from the 'bW General' component.

I have also freshened the reports to give better focus on the issues and to break down the list in to less frightening, more manageable chunks.

{1} Active Tickets, by Priority & Last Updated. {2} Active Tickets by Component {11} Active Bugs by Component {12} Active Feature Requests and Feature Improvements by Component

There are more tickets that i feel can be closed, as 'inactive' issues ie no update for 2-3 years and or that have already been resolved, but not closed on trac

If everyone who knows the history of updates, can spend a little time going through the remaining tickets and close or refresh as many as possible.

If you have tickets assigned to you, that have not been updated 'recently', please update the ticket with at least 1 sentence on the status of the issue.

If you have an intrest in an issue, that has been closed, due to inactivity, please either create a new ticket or reopen the historical ticket. I recommend to, because it was often obvious why a ticket hadn't been resolved, which many times was because it didn't have enough information in it or a clear enough description. So it is worth writing a bright fresh new ticket, which will probably get more attention, for that fact alone.

If the ticket is valid, but inactive, it will help it to come into focus, if you update any issues you want to encourage. Please don't just do 'Up' and 'Bump' updates, but take the time to write at least a sentence.

Looking at the bugs by component, there are only 93. Some components only have 1 or a few bugs. If would be great to get components bug free. Few of these bugs are critical or major, which is positive. We should focus on having 0 blocker and critical issues, currently we need to resolve 17 of these issues. Maybe some of these have been over dramatically prioritised and can be reprioritised, to reduce this number.

Then we can start looking at the improvement requests, 161 these are not a lot really and i think most of them would evaporate with a focused and systematic comb, through each component. 30 of these are profile and account issues, another 15 a piece for groups and fourms, that's 40% of the tickets resolved and three areas updated in as many weekend ehackathons.20 tickets a week? Including tickets resolved at the hackathons.

Its a bit tragic and geekie, to admit, but I do like a short issue/work list, I've worked on many IT helpdesk systems, but i think i really get it from being a pizza driver, when i was studying. Pizza in the racks means lost tips. There is a kinda nice peace, when you do clear down a list, like ahhh, everythings alight in my world.

You know what happens, when we don't have any work? We play! I think this is where bW can then really shine and be all that it can be, which is everything or just anything it chooses. We will get more done, when we have no work.

I hope you find it clearer too.

LnP

Trac looks like a great tool that will help us get to where we want to be.

Does trac have any form of profile, with skills, availability times? This would help us make the most of the communities contributions.

Change History (8)

comment:1 Changed 6 years ago by TimLoal

  • Owner changed from planetcruiser to TimLoal
  • Status changed from new to assigned

comment:2 Changed 6 years ago by TimLoal

Reports can be edited by any one and can be left in a broken state. The following are the working queries for each report.

{1} Active Tickets, by Priority & Last Updated.

SELECT p.value AS color,

t.priority AS group,

id AS ticket, summary, component, version, milestone, t.type AS type, owner, status, 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 <> 'closed' ORDER BY t.priority, t.type, changetime DESC

{2} Active Tickets by Component

SELECT p.value AS color,

component AS group, id AS ticket, summary, version, version, t.type AS type, owner, status, 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 <> 'closed' ORDER BY (component IS NULL),component, t.type, p.value, time DESC

{3} Active Tickets by Milestone

SELECT p.value AS color,

milestone
' Release' AS group,

id AS ticket, summary, component, version, t.type AS type, owner, status, 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 <> 'closed' ORDER BY milestone, (milestone IS NULL), p.value, t.type, time

{4} Active Assigned Tickets, by Owner

SELECT p.value AS color,

owner AS group, id AS ticket, summary, component, milestone, t.type AS type, 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 = 'assigned' ORDER BY owner, p.value, t.type, time

{5} Active Assigned Tickets, by Owner (Full Description)

SELECT p.value AS color,

owner AS group, id AS ticket, summary, component, milestone, t.type AS type, time AS created, description AS _description_, changetime AS _changetime, reporter AS _reporter

FROM ticket t LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority' WHERE status = 'assigned' ORDER BY owner, p.value, t.type, time

{6} All Tickets By Milestone (Including closed)

SELECT p.value AS color,

t.milestone AS group, (CASE status

WHEN 'closed' THEN 'color: #777; background: #ddd; border-color: #ccc;' ELSE

(CASE owner WHEN '$USER' THEN 'font-weight: bold' END)

END) AS style,

id AS ticket, summary, component, status, resolution,t.milestone,version, t.type AS type, priority, owner, changetime AS modified, time AS _time,reporter AS _reporter

FROM ticket t LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority' ORDER BY (milestone IS NULL), milestone DESC, (status = 'closed'),

(CASE status WHEN 'closed' THEN modified ELSE (-1)*p.value END) DESC

{7} My Tickets

SELECT p.value AS color, component AS group,

id AS ticket, summary, component, version, milestone, t.type AS type, priority, 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 t.status <> 'closed' AND owner = '$USER' ORDER BY (status = 'assigned') DESC, p.value, milestone, t.type, time

{8} Active Tickets, Mine first

SELECT p.value AS color,

(CASE owner

WHEN '$USER' THEN 'My Tickets' ELSE 'Active Tickets'

END) AS group,

id AS ticket, priority, summary, component, version, milestone, t.type AS type, owner, status, 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 <> 'closed' ORDER BY (owner = '$USER') DESC, p.value, milestone, changetime, t.type, time

{9} Tickets modified in the last 24 Hours

query:?changetime=1dayago.. & report=9 & desc=1 & order=changetime

{10} Tickets modified in the last 7 days

query:?changetime=1weekago.. & report=10 & desc=1 & order=changetime

{11} Active Bugs by Component

SELECT p.value AS color,

component AS group, id AS ticket, summary, owner, status,t.type, t.priority, 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 <> 'closed' AND t.type = 'bug' ORDER BY (component IS NULL),component, t.type, t.priority, changetime

{12} Active Feature Requests and Feature Improvements by Component

SELECT p.value AS color,

component AS group, id AS ticket, summary, t.type AS type, milestone, owner, status, t.priority, 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 <> 'closed' AND (t.type = 'improve feature' OR t.type = 'new feature') ORDER BY (component IS NULL),component, t.type, p.value, time

{13} Active Tickets by Version

SELECT p.value AS color,

component, id AS ticket, summary, version AS group, version, t.type AS type, owner, status, 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 <> 'closed' ORDER BY (version IS NULL),version, p.value, t.type, time

LnP

comment:3 Changed 6 years ago by TimLoal

  • Priority changed from critical to major

comment:4 Changed 6 years ago by TimLoal

I have created a 'Legacy Resolved' Milestone and have moved 500 unassigned to it. It is still open, whily i continue to tidy up. I found another ~400 tickets, which have no milestone and will move them also, when, I'm sufficiently bored. Would love to be able to just run a query over them.

There are now no or very few, tickets that do not have a ticket type or component. I now plan to comb through each component, to make sure, they are correctly associated with the right component and of an appropriate type.

I feel it would be beneficial to define the grades of tickets, so that we can use these flags consistently. It will be also useful to create more components with in trac, to better categorise tickets.

Such as BW Signup, BW Security, BW Communication, BW Events.

Hopefully, all this has made things a lot clearer, easier to use and will better help us to stay on Track. :)

LnP

comment:5 Changed 6 years ago by TimLoal

  • Status changed from assigned to accepted

comment:6 Changed 6 years ago by TimLoal

  • Priority changed from major to minor
  • Type changed from developer task to volunteer task

I have paused this task for a while to let things settle.

the remainder of the tasks are more about getting rid of the rubbish(400+ spam, test, empty and poorly written tickets) and archiving historical tickets unrelated to current systems or code. ie BV Forums, etc

I hope whoever has admin access on track can work with me to improve how trac works for us. One question I have is, can we use the severity field to mark the severity of the issue and use the priority field to move issues up and down the list of things to do next, amongst ourselves or to reflect the importance to the community and member's UX. We can also make use of the voting system on trac to boost supported tickets.

Track seems to be running slowly, I'm not sure if there is any db admin tools, ie compact and repair, that can be run over the trac db? Or maybe that we need to reduce the size of the database or give trac more processing power. Who looks after Trac?

LnP

comment:7 Changed 6 years ago by jsfan

  • Milestone Future deleted

Milestone Future deleted

comment:8 Changed 6 years ago by shevek

  • Milestone set to unassigned
  • Resolution set to wontfix
  • Status changed from accepted to closed

Closing.

Note: See TracTickets for help on using tickets.