ticket,summary,type,release,owner,status,created,modified,_description,_reporter
14243,Unable to use pipe-delimiting syntax for Set rule,defect,1.4,Ryan J Ollos,new,2023-08-30T05:11:13+02:00,2023-08-30T05:24:00+02:00,"I'm trying to set one value in response to another and it is only working if I use a single value.  Trying to have multiple listed does not respond.  I have the following setup under the tickets-custom: 
{{{
cfc = select 
cfc.label = Critical Facility Capability
cfc.options = |Electrical|Hydraulic
cfc.order = 2
cfc.value =
itemcode = select
itemcode.value =
itemcode.label = Item Code
itemcode.order = 6
itemcode.options = |BCA|BAC|BNE|P400|HPU|NPW
}}}
I then have these two rules setup:
{{{
cfc.set_to_Electrical_when_itemcode = BCA|BAC|BNE|P400  (overwrite)
cfc.set_to_Hydraulic_when_itemcode = HPU|NPW (overwrite)
}}}
Written as above, they do nothing, but if I remove all but the first option for each rule then setting my itemcode field to BCA will set cfc to Electrical, and setting it to HPU will set it to Hydraulic.  

Unsure where to go from there. ",Alfred
8400,Trigger off ticket status not type,enhancement,0.11,,new,2011-01-14T22:46:37+01:00,2019-11-06T20:35:59+01:00,"It would be nice to hide or show fields based upon the ticket status.  We have custom fields that need to be filled out based upon the status.  If the ticket is fixed, some special fields are filled out.  There are additional fields that need to be filled out if the ticket is in the verified state.  Only showing the fields for a particular ticket status would be helpful.",agsiegel@…
13153,TracTicketFieldsLayoutPlugin incompatible with hiding/showing fields via DynamicFieldsPlugin,enhancement,1.0,,new,2017-04-14T17:41:48+02:00,2018-09-21T19:26:05+02:00,"When both [th:DynamicFieldsPlugin] and [th:TracTicketFieldsLayoutPlugin] are enabled, trying to show fields based on type seems to break the ticket layout.",clayton.chu@…
14031,Take into account dynamic fields in email notification,enhancement,1.4,Ryan J Ollos,new,2021-06-02T10:45:26+02:00,2021-06-02T10:45:26+02:00,"As of today, email notifications include all fields. It wouldbe nice to take into account dynamic field configuration to only include relevant fields for a givent ticket type.",mathieu@…
9998,Set rule would benefit from the append option,enhancement,0.12,,new,2012-04-30T17:00:56+02:00,2018-09-21T19:26:05+02:00,"Set rule currently populates a clear field only unless ""overwrite"" is used.
Implementing the append option to this rule would enable the cc field to be appended when a ticket type changed. We use ticket types where some are specific to teams so this option would be extremely useful for team based notifications.",wberry@…
9274,rename fields based on ticket type,enhancement,0.11,,new,2011-10-17T12:51:01+02:00,2020-11-30T20:31:26+01:00,"I'd like to have different label for the ""Summary"" field based on different ticket types. Would love to have a way to configure this. ",anonymous
12871,"Please add ability to set date fields to relative dates, e.g. ""now + 2 weeks""",enhancement,,,new,2016-09-21T09:51:03+02:00,2018-09-21T19:26:05+02:00,"I would like tickets to have a default due date, ideally by priority.

E.g. something like:

{{{
duedate.set_to_now+2weeks_when_priority = normal
duedate.set_to_now+2days_when_priority = urgent
}}}

This would then probably depend on the DateFieldPlugin or Trac 1.1.1+.",Andras Korn
12510,Message at validate rule,enhancement,1.0,,new,2015-09-09T16:08:34+02:00,2018-09-21T19:26:05+02:00,"Hi,

It would be great if it is possible to add a message to the validation rule, because the least users know how a regex work.

And the message `owner must not ^(?!(?:[a-z0-9!#...` is not perfect ;)

example checks if the owner is an email address:
{{{
owner.invalid_if = ^(?!(?:[a-z0-9!#$%&'*+\/=?^_`{|}~-]+(?:\.[a-z0-9!#$%&'*+\/=?^_`{|}~-]+)*|""(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21\x23-\x5b\x5d-\x7f]|\\[\x01-\x09\x0b\x0c\x0e-\x7f])*"")@(?:(?:[a-z0-9](?:[a-z0-9-]*[a-z0-9])?\.)+[a-z0-9](?:[a-z0-9-]*[a-z0-9])?|\[(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?|[a-z0-9-]*[a-z0-9]:(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21-\x5a\x53-\x7f]|\\[\x01-\x09\x0b\x0c\x0e-\x7f])+)\])).*$
}}}

THANK YOU
regards",anonymous
8819,Hide based on handler,enhancement,0.11,,new,2011-05-20T01:10:00+02:00,2020-05-04T22:41:41+02:00,"For instance, hiding a bunch of things for new ticket creation (/newticket), but allowing it to be everywhere else (/query, /ticket, etc).

Unless this functionality exists already, and I'm just not ""getting"" it.",anonymous
14115,Default values are not displayed,defect,1.2,Ryan J Ollos,accepted,2022-02-22T12:56:20+01:00,2022-02-22T17:11:45+01:00,"If I assign a default value to a field and then use `show_when_type` they are no longer displayed (as in ticket #10059). But if I add `.clear_on_hide=false` as described, the fields are displayed in each ticket summary with their default values. Also in ticket types where they are hidden. ",florian.strauss@…
12584,Completely hide ticket fields/columns based on user group,enhancement,0.11,,new,2015-11-20T11:58:08+01:00,2019-07-06T02:36:44+02:00,"an enhancement for using this plugin for very-fine grained permissions.

enhance the show_if_group rule in order to hide fields (and show them only to selected groups) not only in ticket pages, but also:

- in the Custom Query page (possibly by removing the fields from the ""add filter"" dropdown and from the ""Columns"" checkboxes)
- in the ""Available Reports"" (possibly by hiding the columns)",federico.destefanis.work@…
13915,Change ticket field label,defect,,Ryan J Ollos,assigned,2020-12-03T05:29:55+01:00,2020-12-03T05:29:55+01:00,"BlackMagicTicketTweaksPlugin allows field labels to be changed. This is useful for renaming the built-in fields. Custom ticket fields allow the labels to be specified in the `[ticket-custom]` section.

BlackMagicTicketTweaksPlugin is deprecated so the feature should be added to this plugin.",Ryan J Ollos
9597,Add another possible field state (to visible or hidden): read-only,enhancement,0.11,,new,2011-12-09T23:43:06+01:00,2018-09-21T19:26:05+02:00,"Use-case: inform reporter, that some default values are set for him/her, like related component, but reporter should really submit it unaltered, even not by accident. This has the potential of i.e. keeping reports clean without much ticket post-creation clean-up effort.",Steffen Hoffmann