yoheeb at gmail
Nov 23, 2009, 7:12 AM
Post #4 of 4
(448 views)
Permalink
|
|
Re: Custom ticket fields and dependencies
[In reply to]
|
|
On Nov 23, 7:26 am, "Chris Nelson" <Chris.Nel...@sixnet.com> wrote:
> Nir Ben Eliezer wrote:
> > Any chance someone has an answer for this issue?
> > I have a short question about creating custom fields in tickets.
>
> > I need the option to create a "Sub-Component" drop down menu.
> This
> > field should be dependent on the component which the user chose. For
> > example, choosing "component1" will result in the appearance of
> > "sub-component1" and "sub-component2" in the "Sub-Component" drop
> > down menu. Choosing other components may result in the appearance of
> > other sub components.
>
> > Is this possible to implement? I couldn't find any easy
> > configuration which enables this important option.
>
> We accomplished this by having compound components like "main/part1",
> "main/part2", etc. and adding some JavaScript to the ticket handling
> which parses on /, presents just the first part, and adds and populates
> a second list box if the item selected in the first part has
> subcomponents. Trac still thinks that there's only one component field
> (in the db) but users can select subcomponents when creating or updating
> tickets.
well, you should of started a new thread rather than hijack this one
for best results, however...
a better way to accomplish this may be to not use components. Keep
your components higher level, like "Software" "Documentation"
"Hardware"
and use the following plugin:
http://trac-hacks.org/wiki/TracTicketChainedFieldsPlugin
seems like what you are really after
--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=.
|
