Edgewall Software

Opened 9 years ago

Last modified 6 months ago

#4549 new enhancement

[PATCH] Ticket std/custom fields improvements - sql based values, order by, labels, value evals, ...

Reported by: trebor74hr@… Owned by:
Priority: normal Milestone: next-major-releases
Component: ticket system Version: 0.10
Severity: normal Keywords: workflow custom fields
Cc: Ryan J Ollos
Release Notes:
API Changes:

Description (last modified by Christian Boos)


First to say, I find Trac very useful and programmed nicely (appologies for my English).

Revision 5 is trac 0.10. Ticket fields std/custom improvements:

  • field values (combo) filled with sql
  • customized order of fields
  • std fields - customized label/default values
  • values - evaluation of variables

TRAC.INI with samples:

      std fields
      default_* - default values
      order_*   - order by (not applicable for some fields - e.g. ticket title)
      label_*   - labels
      custom fields
      req_who.options   - sql filling the fields
      req_when.value = $(today) - variable evaluation 

I plan to implement following - but the question is when :(

  • obligatory/optional/hidden field definition in ini
  • init ticket callback - can change field definition (value, type, order …)
  • save ticket callback - can check/reject/change field values
  • ticket initialization
  • add to ticket/ticket_change "status by user" (like unread ticket, ticket, …) can be used also as internal mail … instead of sending the mail mark ticket/ticket_change to be read by some users
  • customized home page for the user - will show number of unread tickets newly
  • ticket "factory" for periodical tickets - e.g. one ticket generated for every month

It would be nice to have customized statuses, so in the future trac could be some kind of workflow system (add allowed state-transitions/persons). Each status could have extra fields, e.g. if status is "fixed" then field could be revision number.

Hope this will be useful.

Best regards from Croatia, Robert

Attachments (2)

trac-ulr1-061208.diff (8.9 KB) - added by trebor74hr@… 9 years ago.
trac/ticket/web_ui.py, api.py, trac/web/auth.py
trac.ini (2.2 KB) - added by trebor74hr@… 9 years ago.
sample part of ini file

Download all attachments as: .zip

Change History (10)

Changed 9 years ago by trebor74hr@…

trac/ticket/web_ui.py, api.py, trac/web/auth.py

Changed 9 years ago by trebor74hr@…

sample part of ini file

comment:1 Changed 9 years ago by Christian Boos

  • Keywords workflow custom fields added
  • Milestone set to 1.0

Several interesting ideas… worth to be looked at.

#4374 already requested the ability to generate options from SQL queries.

Also, note that several of your "future" ideas are being worked on in the source:sandbox/pycon/workflow branch. You may want to comment on the WorkFlow page or join the discussions on the trac-dev MailingList.

comment:2 Changed 9 years ago by Christian Boos

See also #2464.

comment:3 Changed 6 years ago by Ryan Ollos <ryano@…>

  • Cc ryano@… added

comment:4 Changed 6 years ago by Christian Boos

  • Description modified (diff)

comment:5 Changed 6 years ago by Christian Boos

  • Milestone changed from 1.0 to unscheduled

Milestone 1.0 deleted

comment:6 Changed 5 years ago by Christian Boos

  • Milestone changed from triaging to next-major-0.1X

Related to FieldRefactoring.

comment:8 Changed 16 months ago by Ryan J Ollos

  • Cc Ryan J Ollos added; ryano@… removed

comment:9 Changed 6 months ago by Ryan J Ollos

  • Owner Jonas Borgström deleted

Modify Ticket

Change Properties
Set your email in Preferences
as new The ticket will remain with no owner.
The ticket will be disowned. Next status will be 'new'.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.