Ticket #7764 (reopened defect)

Opened 3 years ago

Last modified 2 years ago

Using non tcf_ field as the parent of chained fields

Reported by: mehdiru <mehdi@taileb.name> Assigned to: richard
Priority: normal Component: TracTicketChainedFieldsPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.12

Description

Hi, Thanks for the great job! It would be cool if there was a possibility to have standard fields (for example component) as the top-level field. This woudl help me implement a great functionality for my projects: subcomponents :)

Thanks ie. By the way it works for me on trac 0.12

Attachments

screenshot.png (28.4 kB) - added by mehdi@taileb.name on 03/04/11 06:39:33.
Two component fileds!

Change History

10/01/10 05:21:19 changed by richard

  • status changed from new to closed.
  • resolution set to duplicate.

This feature have been implemented in #6684.

10/01/10 05:46:44 changed by mehdiru <mehdi@taileb.name>

  • status changed from closed to reopened.
  • resolution deleted.

THe following configuration doesn't work: 

{
    "component": {
        "Network": {
            "tcf_subcomp": {
                "OpenVPN": {},
                "Trac": {},
                "Mercurial": {}
            }
        },
        "Google Apps": {
            "tcf_subcomp": {
                "": {}
            }
        },
        "Soft infra": {
            "tcf_subcomp": {
                "ModelSim": {}
            }
        }
    }
}

Here "component" is the trac's component list which I prealably configured.

03/03/11 18:22:51 changed by anonymous

This is working for me except I have a bug where the correct values are not being selected as it's only the input type which is searched for.

03/03/11 18:44:28 changed by anonymous

See the patch in #8082 that I came up with and this will work.

03/04/11 04:20:50 changed by richard

  • status changed from reopened to closed.
  • resolution set to fixed.

(In [9928]) Fixed #7764

03/04/11 06:39:33 changed by mehdi@taileb.name

  • attachment screenshot.png added.

Two component fileds!

03/04/11 06:42:38 changed by Mehdi Taileb <mehdi@taileb.name>

  • status changed from closed to reopened.
  • type changed from enhancement to defect.
  • resolution deleted.

In my case is shows two "component" fields!! cf. the attached file (http://trac-hacks.org/attachment/ticket/7764/screenshot.png)

trac.ini: 

[tcf]
chained_fields = component, tcf_subcomp
[ticket-custom]
tcf_subcomp = text
tcf_subcomp.format = plain
tcf_subcomp.label = Sub-Component
tcf_subcomp.order = 0

Chained fields (admin pannel) content: 

{
    "component": {
        "Network": {
            "tcf_subcomp": {
                "OpenVPN": {},
                "Trac": {},
                "Mercurial": {},
                "Firewall":{},
                "MySQL":{},
                "Joomla":{},
                "Security":{}
            }
        },
        "Google Apps": {
            "tcf_subcomp": {
                "Authentication": {}
            }
        },
        "Soft infra": {
            "tcf_subcomp": {
                "ModelSim": {}
            }
        }
    }
}

03/04/11 07:28:04 changed by richard

My environment has no such phenomenon.

[9928] did not touch code for newticket path, so I guess it is caused by something else.

Could you test it with previous version? Or try clear cache and refresh?

Add/Change #7764 (Using non tcf_ field as the parent of chained fields)




Change Properties
Action