Contents
Add custom date fields to tickets and helps date selection
Notice: This plugin is deprecated in Trac 1.2 and later. Custom fields of type time were added in Trac 1.1.1.
Please ask on the MailingList or #11856 if you need help migrating
date fields to Trac's new time
format.
Description
This plugin provides a datepicker for ticket and milestone fields, and validation of the date string for ticket custom fields. It will only validate that the given input has the specified date format (see below). The value is stored in the database as a string, as Trac does not yet have date field support (t:#1942). Note: It is not the intention of this plugin to provide date-type support.
Development News
- Version 3.0.0: The 1.0 branch is a development branch that has been created to support work forwards version 3.0 of the plugin, which will only support Trac 1.0 and later.
- Version 2.0.0: The 0.12 branch is a development branch that has been created to support work towards version 2.0 of the plugin, which will only support Trac 0.12 and later.
- Version 1.1.0: The jQuery UI component has been downgraded to 1.6 to ensure compatibility with jQuery 1.2.6 that ships with Trac 0.11.x.
With release 1.0, Trac has integrated the jQuery UI library along with datepicker and datetimepicker extensions into the core.
Pick a date on tickets and milestones:
0.11 branch ------------------- Development branch
Bugs/Feature Requests
Existing bugs and feature requests for DateFieldPlugin are here.
If you have any issues, create a new ticket.
defect |
44 / 44 |
|
---|---|---|
enhancement |
13 / 13 |
|
task |
5 / 5 |
Source
You can check out DateFieldPlugin from here using Subversion, or browse the source with Trac.
Download
Download the zipped source from here.
Installation
- Install globally with:
sudo easy_install https://trac-hacks.org/svn/datefieldplugin/1.0/
- Enable the plugin by updating TracIni file (..../trac.ini) as follows:
[components] datefield.* = enabled
- Configure the project management support for the plugin in its own configuration section, placed into 'trac.ini' file as follows:
- To add a Due Date, just set up the field as a custom field, or use the CustomFieldAdminPlugin (image right) to create a date field: The example demonstrated use of the special value
[ticket-custom] due_date = text due_date.date = true due_date.label = Due Date # special value <now> works with 1.0 branch only due_date.value = <now> due_date.date_empty = true
<now>
, which is supported only on the 1.0 branch. The value will be replaced with the current date. - Site-wide defaults for macro arguments may be set at the [datefield] section:
More details about them see #Arguments section.
[datefield] format = mdy separator = - first_day = 1
- To add a Due Date, just set up the field as a custom field, or use the CustomFieldAdminPlugin (image right) to create a date field:
- Restart web server on command line:
sudo /etc/init.d/apache2 restart
Arguments
This plugin can be controlled with a number of arguments, inside [datefield]
section contained in trac.ini
configuration file:
Argument | Version | Description | Default value |
format | The format to use for dates. valid formats are dmy , mdy , and ymd | dmy
| |
separator | The separator character to use for dates. Possible values are - or . or / | /
| |
first_day | >= [6118] | First day of the week (0=Sunday .. 6=Saturday) | 0
|
months | >= [7192] | How many months to show at once? | 1
|
milestone | >= [7192] | Use datepicker for milestone due/complete fields? (format= must match your locale) If you turn this on, you must use MM/DD/YYYY for the date format. Set format to mdy and separator to / . | false
|
weeknumbers | >= [7192] | Show ISO8601 week number in calendar? | false
|
panel | >= [7192] | Show panel with a "Today" and "Done" buttons (at bottom)? | false
|
change_month | >= [7192] | Show a dropdown with month selection? | false
|
change_year | >= [7192] | Show a dropdown with year selection? | false
|
match_request | >= [7192] | Use datepicker on arbitrary request paths. Use text fields with class=datepick in your template, and configure the start of request path (in list format), like: match_request = /query,/other_path |
|
months | >= [7192] | Number of months visible in datepicker | 1
|
There are many other options, but you need to modify the datefield.html
template if you want to use them. See jQuery UI Datepicker.
Recent Changes
- 16195 by rjollos on 2017-01-21 22:49:11
-
3.0.0: Set Trac version requirements
- 14902 by rjollos on 2015-09-15 22:52:02
-
3.0.0: Release version 3.0.0 of plugin.
- 14901 by rjollos on 2015-09-15 22:46:43
-
3.0.0dev: Fixes error in handling of
<now>
keyword.
The keyword replacement was not being applied to each field independently. Fixes #12512.
(more)
Author/Contributors
Author: coderanger
Maintainer: Ryan J Ollos
Contributors: doki_pen, terje
Attachments (4)
-
Sample_Report.txt (720 bytes) - added by 17 years ago.
Example of using date field in a report.
- customfields.jpg (6.2 KB) - added by 15 years ago.
-
DateFieldPlugin.png (13.0 KB) - added by 13 years ago.
DateFieldPlugin at version 1.0.3
- DatePickerTrac011.png (14.7 KB) - added by 13 years ago.
Download all attachments as: .zip