Context Navigation

Changes between Initial Version and Version 1 of Ticket #12899, comment 2

initial	v1
2	2
3	3	I was using the version from trunk, but I just reverted to the 1.0 tag, and still see the same behavior. I don't see any problem with the TracTicketChainedFieldsPlugin functionality either, in either branch. Maybe there is some other contributing factor in my configuration? I'm using the trac package in Debian stable/8/jessie (that's version 1.0.2+dfsg-2), and I do have other plugins installed/enabled (BatchMod, CustomFieldAdmin, LDAPPlugin, TracRPC, TracTags, TracWYSIWYG, FieldTooltip, TracTicketTemplate), and several other custom fields which display after the chained fields. I'll attach my config file (with project identifiers replaced with "FOO"), if that will help.
	4	(EDIT: I also attached a TracTicketChainedFieldsPlugin JSON file that will work with the fields set up in the trac.ini)
4	5
5	6	I thought about using the kis_assistant to automatically generate the menu hierarchy as you suggest, as it would be nice to remove TracTicketChainedFieldsPlugin (it doesn't look like it's maintained, as it has several years-old bug reports). I'll have to ponder this approach some more. In this instance, the chained fields JSON structure is dynamically generated from another set of JSON files which are maintained elsewhere (all I have is a set of URLs to fetch the files from). So I'd have to figure out how to automatically generate the somewhat complex kis_assistant config from that JSON, and insert it into the .ini file from a script dynamically.