﻿ticket,summary,type,release,owner,status,created,modified,_description,_reporter
12103,Adding other custom fields will delete the effect of the TracTicketChainedFieldsPlugin,defect,1.0,,new,2014-12-10T10:03:13+01:00,2019-09-04T19:39:29+02:00,"Hello, 
I am using trac 1.0.1 Windows server:[[BR]]
my trac.ini is joined to this ticket.[[BR]]

When I try to add another custom field to my ticket the effect of chained fiels (priority, impact, criticie) will disappear.[[BR]]


could you help me to fix this problem.[[BR]]

Thank you .
",raafet.dormok
11492,chained fields deleted when viewing ticket,defect,1.0,,new,2014-01-10T12:48:39+01:00,2020-05-06T02:05:20+02:00,"Hi,
I have installed and configured TrackTicketChainedFieldsPlugin with two custom fields as a chained fields and I can create new ticket without problems. But I have two issues that I think could be related:
1. When I create a new ticket, chained fields show two undesired values ("""" and ""undefined"")
2. When I view a ticket that has values on chained fields, that values are deleted automatically and the history shows:
=== Changed by USERNAME ===
* FIELD_NAME FIELDVALUE deleted (revert)

I can revert, but when I view the ticket, the chained fields are deleted again.

How can I solve this?

Thanks in advance,
Quimi
",jfernandez@…
11473,incompatibility with TracTicketTemplate,defect,1.2,Richard Liao,new,2014-01-03T18:35:50+01:00,2014-01-03T18:35:50+01:00,"Hi,

Why is TracTicketTemplate incompatible ? Is there any workaround to have the 2 plugins available ?

Like said in the doc, if TracTicketTemplate is installed and you try to activate it (even if TracTicketChainedFields plugin is disabled), trac won't work any more.",anonymous
9298,mark some entries as the default,defect,0.11,Richard Liao,new,2011-10-20T16:55:33+02:00,2011-10-20T16:55:33+02:00,"Hi, I am trying to use the plugin to simulate subcomponents. For this I let the plugin control the component field, and also some subcompoenent field. now the default of component has no effect any more, and also for subcomponents there should be a better default, can you make it so that you can mark one of the items as selected?

it would also be nice if you could make some items stand out, like be always on top or  bottom so one can put some ""Other"" or similar there, so that people dont have to search it in the list.",anonymous
9295,allow easier configuration,enhancement,0.11,Richard Liao,new,2011-10-20T13:07:50+02:00,2013-09-20T14:06:34+02:00,"The configuration of the json string is quite error prone, especially when it grows very large (we have hundreds of entries). It would be nice if a javascript component could be added to the administrative panel that would parse the json, and display the dropdowns and make the single lists editable easily.

my idea of this would be that when you have like, level0, level1 etc. fields then there will be a dropdown for level0 along with an editbox beside it where you can change all entries in level0. then depending on what is selected in level0 there will be a level1 displayed with an edit box beside it for all level1 things and so on.",anonymous
8956,Chained Fields pull down lists not working in Internet Explorer 8.0 with Trac 0.12,defect,0.12,Richard Liao,new,2011-07-07T17:16:29+02:00,2011-07-07T17:16:29+02:00,"We recently upgraded our system from 0.11 to 0.12, and we discovered that the chained fields do not display properly in internet explorer 8.0 (have not tried any other version of IE).  They used to display fine, but now the pull down is very small so that you cannot read the values in the list. I will be telling our team to use firefox or chrome, so it's not an urgent issue for us, but i wanted to report the defect.",sue.sml2006@…
8683,allow text-fields to be chained,enhancement,0.12,Richard Liao,new,2011-04-07T15:51:15+02:00,2011-04-08T12:55:17+02:00,"
One of my projects asked me whether it's possible to use chained-fields to
set ""Cc:"" depending on the selected component. So I had a closer look to your
plugin and after some playing around, I did some modifications (see attached
patch).

At least here it is working (I'm still doing more testing).

Could you please have a look at the patch and confirm that I'm not doing any 
changes that influence the normal behaviour of your plugin?
(I'm neither a javascript- nor a jquery-programmer, so I'm a little afraid to
break some functionality with my changes...)

Thanks a lot!



",Christian Masopust
8630,Provide an option to not sort the drop down alphabetically,enhancement,0.11,Richard Liao,new,2011-03-22T16:21:37+01:00,2012-09-13T17:28:54+02:00,"Chained fields drop downs are currently sorted alphabetically, but this can result in an uncommon value being shown first, when the designer may wish to have some other more common value be the default.  ",sue.sml2006@…
8082,"Using ""component"" as parent of chained fields resets value on modify",defect,0.11,Richard Liao,reopened,2010-11-18T11:48:24+01:00,2012-06-06T14:56:06+02:00,"I have ""component"" set as the parent field for my custom chained fields. When I go to edit a ticket, the value in the component field is the default value, and I have to change this back to the correct one manually to avoid changing the ticket's component.",afrogamer@…
