Modify

Opened 10 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)

trac_raafet.dormok.ini (9.0 KB) - added by raafet.dormok 10 years ago.
trac.ini (8.7 KB) - added by raafet.dormok 10 years ago.
ticket.raafet.dormok.png (168.7 KB) - added by raafet.dormok 10 years ago.

Download all attachments as: .zip

Change History (12)

Changed 10 years ago by raafet.dormok

Attachment: trac_raafet.dormok.ini added

comment:1 Changed 10 years ago by raafet.dormok

sorry my my chained filds:

{
    "tcf_priorite": {
        "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": {}
                    }
                }
            }
        }
    }
}
Last edited 10 years ago by Jun Omae (previous) (diff)

comment:2 in reply to:  description Changed 10 years ago by Ryan J Ollos

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 10 years ago by raafet.dormok

Attachment: trac.ini added

Changed 10 years ago by raafet.dormok

Attachment: ticket.raafet.dormok.png added

comment:3 Changed 10 years ago by raafet.dormok

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:

  1. I have still the difficulty to add easily an other custom field , without losing the good functioning of chained fields
  2. The behavior of the priority field which I chained with the two other custom fields impact and criticite 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": {}
                    }
                }
            }
        }
    }
}
Last edited 10 years ago by Ryan J Ollos (previous) (diff)

comment:4 Changed 10 years ago by Ryan J Ollos

Owner: changed from Richard Liao to Ryan J Ollos
Status: newaccepted

comment:5 Changed 10 years ago by raafet.dormok

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 10 years ago by anonymous

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 10 years ago by Ryan J Ollos

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 10 years ago by Ryan J Ollos

Summary: Adding other custom fileds will delete the effect of the TracTicketChainedFieldsPluginAdding other custom fields will delete the effect of the TracTicketChainedFieldsPlugin

comment:9 Changed 8 years ago by Ryan J Ollos

Owner: Ryan J Ollos deleted
Status: acceptednew

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.