Opened 9 years ago
Last modified 5 years ago
#12103 new defect
Adding other custom fields will delete the effect of the TracTicketChainedFieldsPlugin
Reported by: | raafet.dormok | Owned by: | |
---|---|---|---|
Priority: | highest | Component: | TracTicketChainedFieldsPlugin |
Severity: | blocker | Keywords: | |
Cc: | Trac Release: | 1.0 |
Description
Hello,
I am using trac 1.0.1 Windows server:
my trac.ini is joined to this ticket.
When I try to add another custom field to my ticket the effect of chained fiels (priority, impact, criticie) will disappear.
could you help me to fix this problem.
Thank you .
Attachments (3)
Change History (12)
Changed 9 years ago by
Attachment: | trac_raafet.dormok.ini added |
---|
comment:2 Changed 9 years ago by
Replying to raafet.dormok:
When I try to add another custom field to my ticket the effect of chained fiels (priority, impact, criticie) will disappear.
Please include the exact edit you make that causes the chained fields to disappear.
Changed 9 years ago by
Changed 9 years ago by
Attachment: | ticket.raafet.dormok.png added |
---|
comment:3 Changed 9 years ago by
Thank you for giving interest to my request,
I am delighted for our exchange, I am implementing trac for a BANK
below I provide you the edit exactly and I attach my trac.ini file to this ticket after some changes.
otherwise, I disabled totally the TracTicketChainedFieldsPlugin and I added some custom fields (as you can see in my attach example ticket file) and thereafter I activated again the same plugin however the chained fields (priority
, tcf_impact
, tcf_criticie
) is working. but some bad behavior bothers me as I marked in red in my attach ticket
I summary:
- I have still the difficulty to add easily an other custom field , without losing the good functioning of chained fields
- The behavior of the priority field which I chained with the two other custom fields
impact
andcriticite
is not practical
I count on you to help me thank you in advance
{ "priority": { "faible": { "tcf_impact":{ "reduit": { "tcf_criticite":{ "mineur": {} } }, "limite": { "tcf_criticite":{ "mineur": {} } }, "etendu": { "tcf_criticite":{ "mineur": {} } } } }, "moyenne": { "tcf_impact":{ "reduit": { "tcf_criticite":{ "mineur": {} } }, "limite": { "tcf_criticite":{ "majeur": {} } }, "etendu": { "tcf_criticite":{ "majeur": {} } } } }, "haute": { "tcf_impact":{ "reduit": { "tcf_criticite":{ "majeur": {} } }, "limite": { "tcf_criticite":{ "critique": {} } }, "etendu": { "tcf_criticite":{ "critique": {} } } } } } }
comment:4 Changed 9 years ago by
Owner: | changed from Richard Liao to Ryan J Ollos |
---|---|
Status: | new → accepted |
comment:5 Changed 9 years ago by
Hi,
May still hope to receive a response for my request? I have to implement an emergency solution and I think perhaps to avoid to use priority as a core field by replacing with a custome field....
comment:6 Changed 9 years ago by
Happy new year Mr rjollos and all my best wishes
hope your are still giving interest for my problem. I will be very happy to receive the fix.
thank you
comment:7 Changed 9 years ago by
It will be a few more days before I can take a look since I'm working on preparing the Trac release, however I won't forget about the issue.
comment:8 Changed 9 years ago by
Summary: | Adding other custom fileds will delete the effect of the TracTicketChainedFieldsPlugin → Adding other custom fields will delete the effect of the TracTicketChainedFieldsPlugin |
---|
comment:9 Changed 7 years ago by
Owner: | Ryan J Ollos deleted |
---|---|
Status: | accepted → new |
sorry my my chained filds: