|Version 4 (modified by robguttman, 6 years ago) (diff)|
Dynamically hide, default, copy, clear, etc. ticket fields
- Hide a field based on another field's value
- Default a field's value per user preference
- Clear a field's value when another field's value changes
- Copy one field's value to another field
To enable the plugin:
[components] dynfields.* = enabled
See the examples section below for how to specify rules.
If you have any issues, create a new ticket.
Download the zipped source from [download:dynamicfieldsplugin here].
This plugin currently includes four rules. Each rule is specified by modifying the [ticket-custom] section of trac.ini. Below are several examples to motivate using each rule.
Let's say that your team only specifies effort for enhancements, but not for defects or other ticket types. This rule shows a custom effort field only when the type field's value is enhancement:
[ticket-custom] effort.show_when_type = enhancement
If your version field is based upon the milestone, then this rule hides the version field when the milestone field's value is empty:
[ticket-custom] version.hide_when_milestone =
Some of your fields may be auto-generated or used by very few people. To always hide a field:
[ticket-custom] alwayshidden.show_when_type = invalid_value alwayshidden.clear_on_hide = false
The clear_on_hide option above specifies that the field's value should not be cleared when hidden (which is the default behavior).
In the version/milestone example above, if the milestone changes then we want the version field to be cleared:
[ticket-custom] version.clear_on_change = milestone
Let's say your workflow includes reassigning a ticket's owner to someone else for review or verification but maintain the person responsible for the work in a custom captain field. Initially the captain should be set to the owner, so to reduce data entry in making this so:
[ticket-custom] captain.copy_from = owner
Default value rule
Let's say your QA team usually creates defect tickets and your product managers usually create enhancement tickets. Here's how to allow each user to set the default value for the ticket type:
[ticket-custom] type.default_value = (pref)
The above example introduces the plugin's user preference facility described next.
Any rule expressed above can be configured to allow users to set preferences for them by appending (pref) to the end of the rule. For example, here's one of the hide rules from above:
[ticket-custom] alwayshidden.show_when_type = invalid_value (pref)
The (pref) will cause this rule to be added to a new Dynamic Fields preference panel where the user can disable the rule by unchecking the rule's checkbox. Some rules require user input such as the default value rule above. In that example, the user can both enable/disable the rule as well as set the field's default value for him/her.
Extensibility (implementation details)
Rules are implemented as Trac extension points to allow for new rules to be added fairly easily. Four rules come packaged to provide the dynamic behaviors described above. Each rule is split between two parts:
- rule specification (Python in rules.py)
- 15378 by rjollos on 2016-03-01 02:52:44
2.2.0: Bump version to 2.2.0
- 15124 by rjollos on 2015-12-17 21:30:07
2.2.0dev: Fix regression in 
Scripts and stylesheet should only be added for the query,
ticket and newticket realms.
- 15114 by rjollos on 2015-12-11 07:59:06
2.2.0dev: Fix regression in 
Fields were improperly hidden on initial page load.