Opened 10 years ago
Closed 10 years ago
#11922 closed enhancement (wontfix)
Auto populate date field when workflow status is changed.
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | 1.1dev |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I've been struggling with this issue for some time now, I manage a few trac instances for multiple projects; in all cases however, I am finding getting engineering to change the "fixed date", "resolved date", and even the "reopened date" manually when adding to there trac tickets. As a stop gap I have created a database trigger to update the date fields of each workflow status when a ticket is completed, however would find it extremely useful to have this as a function of trac rather than having to build triggers within the database itself. Is this on the horizon to be implemented? Is there a "plugin" that best resolves this issue? Does a database trigger best resolve this issue?
Attachments (0)
Change History (1)
comment:1 by , 10 years ago
Keywords: | Auto populate fields removed |
---|---|
Milestone: | next-dev-1.1.x |
Priority: | high → normal |
Resolution: | → wontfix |
Status: | new → closed |
You could pull the information from the ticket_change table rather than having dedicated custom fields. You would need to modify the template to insert the data; that could be done in
post_process_request
(TracDev/PluginDevelopment/ExtensionPoints/trac.web.api.IRequestFilter).Another alternative would be to conditionally populate the custom ticket fields using jQuery. Or you could force the user to populate them using th:DynamicFieldsPlugin; and there are other plugins that force validation that don't use JavaScript.
If you have further questions, please raise them on the MailingList. You'll reach a broader audience of Trac users. This particular feature is outside the scope of Trac.