Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#1730 closed volunteer task (invalid)

Trac Admin

Reported by: TimLoal Owned by: TimLoal
Priority: major Milestone:
Component: Trac Keywords: Trac, Resolve Ticket Reason, BW Component
Cc:

Description

Is it possible to have access to the application admin end of trac?

I would like to try and sharpen up this tool, so that it does what we want with ease.

A couple of things during the clean up of the tickets, was a few missing or useful components and states. The following lists are my draft recommendations. Components: BW Account BW Login BW Signup BW Security BW Communications(ie newsletter, member updates) BW Organisation BW Security BW Events BW Internationalization RENAMED to BW Translations

Resolution States: Inactive Not Reproducible Housekeeping Insufficient Info Problem resolved due to major work on component

If I can't get in, could someone with access have a look at the feasibility of adding some or all of these options?

Thanks

LnP

Change History (8)

comment:1 Changed 6 years ago by TimLoal

I feel that a more complete look at the life-cycle of a trac ticket, through the processes of resolution in bW, would provide a better understanding of useful and beneficial ticket states, to have and use.

Using what we have, we can make trac ticket lists much more positive, by assigning most if not all of the tickets, rather than most of them being 'Unassigned'.

It would be useful to add an 'In Progress' state, so that it is easy to identify work in progress.

'Fixed' is not the end of the issue. The fix needs to be 'Ready for Beta Testing', 'In Beta Testing', then 'Ready to Merge', 'Alpha Testing',then marked as 'Live Ready' and Finally Closed 'Live'.

These additional states would give much more meaning and information to the tickets. They also give mission goals to work towards, which is positive and also give encouragement to people working on other things, that things are progressing. It is also more positive for any casual member who has a look around trac. It also give an easy view of issues that are ready for testing or to go live and can be pumped in to the alpha or live build.

For the moment, we should make more use of the 'Accepted' state as 'In progress', but we need more, to really streamline and clarify our processes

LnP

Last edited 6 years ago by TimLoal (previous) (diff)

comment:2 Changed 6 years ago by TimLoal

Is it possible for someone to run the following on the track DB?

UPDATE ticket SET milestone='Legacy Resolved' WHERE (milestone='unassigned' OR milestone=) AND status='closed'

This would help clean up and contain the legacy tickets and help us to view and focus on live issues.

LnP

comment:3 Changed 6 years ago by TimLoal

  • Priority changed from major to critical

The above query has been half done manually, but the other half, doesn't justify the time.

Is it possible for someone to run the following on the track DB?

UPDATE ticket SET milestone='Legacy Resolved' WHERE (milestone='unassigned' OR milestone=) AND status='closed'

Thanks to anyone who can do this for me.

LnP

comment:4 Changed 6 years ago by TimLoal

  • Status changed from new to assigned

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 critical to major

Does anyone even know who does have this access?

Who has full sql access to the database and can run a few reviewed update and delete queries or run sql to html for archiving and public access?

Trac is the engine of bW, making it run smoothly is key to the whole project.

LnP

comment:7 Changed 6 years ago by jsfan

  • Resolution set to invalid
  • Status changed from accepted to closed

comment:8 Changed 6 years ago by jsfan

  • Milestone Future deleted

Milestone Future deleted

Note: See TracTickets for help on using tickets.