Opened 4 years ago

# query for root and milestone

Reported by: Owned by: didley@… ChrisNelson normal TracJsGanttPlugin normal 0.12

I'm using ChildsTicketPlugin

I want to display all tickets for a milestone XXX and a special type with all childs.

Which parameter have I to use?

When I use for example [[TracJSGanttChart(milestone=XXX, type=enhancement, etc)]] it shows me only first level of tickets because I can't use the root parameter. If I would use the root parameter makes milestone no sense because I have to put in all numbers of tickets.

Is there a possibility to combine parameter in this way?

### comment:2 Changed 4 years ago by rjollos

• Description modified (diff)

### comment:3 in reply to: ↑ description Changed 4 years ago by ChrisNelson

... When I use for example [[TracJSGanttChart(milestone=XXX, type=enhancement, etc)]] it shows me only first level of tickets because I can't use the root parameter. If I would use the root parameter makes milestone no sense because I have to put in all numbers of tickets.

Is there a possibility to combine parameter in this way?

You might try

[[TracJSGanttChart(root=###,display=milestone:xxx)]]


But I haven't tried the display filter with milestone.

### comment:4 follow-ups: ↓ 5 ↓ 6 Changed 4 years ago by didley@…

Thank you for your suggest. Are you sure you mean to put in parameter root with three hash keys? Nevertheless I got the message

Error: Macro TracJSGanttChart(root=###, display=milestone:0.00 Redesign_Modelcode) failed

Invalid query constraint value


My wish is it should work with other grouping parameter also. For example

and so on.

didley

### comment:5 in reply to: ↑ 4 Changed 4 years ago by didley@…

Sorry. I put in a macro sequenz. I mean this

TracJSGanttChart(root=###,display=owner:xxx)

### comment:6 in reply to: ↑ 4 Changed 4 years ago by ChrisNelson

Thank you for your suggest. Are you sure you mean to put in parameter root with three hash keys?

No, I meant that as a placeholder for one or more ticket IDs:

TracJSGanttChart(root=1|7,display...)]]


...

### comment:7 follow-up: ↓ 8 Changed 4 years ago by didley@…

That's what I won't to do.

As I wrote makes it no sense to put in a milestone, what means I want filter group of particular Tickets, after that I have to put in all singular tickets of this group in parameter root like root=ticket1|ticket2|and so on to show the hierarchie.

Best way would be root=<yes|no>

Maybe it makes sense for you also.

### comment:8 in reply to: ↑ 7 ; follow-up: ↓ 9 Changed 4 years ago by ChrisNelson

That's what I won't to do.

As I wrote makes it no sense to put in a milestone, what means I want filter group of particular Tickets, after that I have to put in all singular tickets of this group in parameter root like root=ticket1|ticket2|and so on to show the hierarchie.

Best way would be root=<yes|no>

Maybe it makes sense for you also.

I am sorry but that does not make sense to me. I guess Engligh is not your first language. I am sure your English is better than my German but you may have to rephrase your comments.

### comment:9 in reply to: ↑ 8 Changed 4 years ago by falkb

That's what I won't to do.

As I wrote makes it no sense to put in a milestone, what means I want filter group of particular Tickets, after that I have to put in all singular tickets of this group in parameter root like root=ticket1|ticket2|and so on to show the hierarchie.

Best way would be root=<yes|no>

Maybe it makes sense for you also.

I am sorry but that does not make sense to me. I guess Engligh is not your first language. I am sure your English is better than my German but you may have to rephrase your comments.

He expressed with German grammar and wanted to write: "As I wrote before, it makes no sense to set a milestone as chart parameter; which means that what I actually want to do is, firstly, to filter a group of particular tickets, and after that I set all tickets numbers of this filter-result as values of parameter 'root', like for example root=ticket1|ticket2|...|ticketN to show the hierarchy."

Furthermore he suggests to just support a parameter 'root' with 2 possible values 'yes' and 'no'. If one configured

[[TracJSGanttChart(root=yes, milestone=XXX, type=enhancement)]]


the chart would show all tickets of milestone XXX and of type enhancement plus all their child tickets. This sounds to me as if all parametrized conditions simply should just apply to the root tickets, and the rest of the child and grandchild tickets is displayed without condition.