Hello guys,

Before open a ticket, i would like to talk a bit about a big problem , that
i'm getting here.
Sorry for my pour english ok. !! Oo

We have used the trac around 5 years.  My version is not the lastest, i use
Trac 0.12.4.
I have developed some issues and fixes on my enviroment for internal use
only.

The Code :

In ticket/api.py there is this code on get_ticket_fields method :

  # Default select and radio fields
        selects = [('type', model.Type),
                   ('status', model.Status),
                   ('priority', model.Priority),
                   ('milestone', model.Milestone),
                   ('component', model.Component),
                   ('version', model.Version),
                   ('severity', model.Severity),
                   ('resolution', model.Resolution)]

        for name, cls in selects:

            options = [val.name for val in cls.select(self.env, db=db)]

            if not options:
                # Fields without possible values are treated as if they
didn't
                # exist
                continue
            field = {'name': name, 'type': 'select', 'label': name.title(),
                     'value': self.config.get('ticket', 'default_' + name),
                     'options': options}
            if name in ('status', 'resolution'):
                field['type'] = 'radio'
                field['optional'] = True
            elif name in ('milestone', 'version'):
                field['optional'] = True
            field['standard'] = True
            fields.append(field)
   ......


The Problem:

We have use trac a lot and today we have exactly 428 milestones completed.
There is a escalability problem. Because on some pages, for example:
roadmap, and ticket view or new ticket, the system uses common code to
provide ticket infos.  If i got it correctly TicketSystem is the central
source of these infos ok ?
But today I need wait about 16 seconds to view the ROADMAP page and this is
a progressive problem.

The question is :  the list of all millestones only is necessary to CRUD
ticke views.  Edit, Insert , etc.

But today, when i request the roadmap view.  The trac selects all tickets
for all milestones and for each ticket the TicketSystem selects all
milestones.
Could you help me ? Well, if you cannot help me, no problem.  But i could
alert you about it. because to enteprise use of trac, this is a problem.
And today i believe the trac is the better system to little and middle size
companies.  I have experiment Jira system.  But for me,  is a Cannon to kill
an ant. =P .  Trac is a simple and effective SCM system.

Well, thanks very much,
Best Regards,


Eduardo L. Fabricio
Java Developer / SCM manager.

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

Reply via email to