ticket,summary,type,release,owner,status,created,modified,_description,_reporter
7427,width has no effect on inline mode,defect,0.11,Shun-ichi Goto,reopened,2010-07-28T16:24:00+02:00,2014-06-24T15:29:54+02:00,"I try to limit the width of an inline'd box. But is seems, that this option has no effect.

{{{[[TicketBox('Open bugs: %d', [query:Type=defect&Status!=closed], 300px, inline)]]}}}",walther@…
1929,Show only totals in Ticket Box,enhancement,0.11,Shun-ichi Goto,assigned,2007-08-14T05:16:18+02:00,2009-05-05T09:06:42+02:00,"I think a great feature for TicketBoxMacro would be to have it list only the total of tickets found in that report. This would be specially useful for using many boxes and/or boxes for reports that have lots of tickets.

Something like this:
{{{
- Active -
|   29   |
----------
}}}",humberto@…
3716,TicketBoxMacro does not obey trac permissions,defect,0.10,Shun-ichi Goto,new,2008-09-12T21:27:26+02:00,2008-09-12T21:27:26+02:00,"
On my trac enviroment, anonymnous users are allowed to see *only* the wiki. But I have TicketBoxMacro ''running'' on the wiki start page. And that's the problem.

When I open the wiki as a anonymous user, the macro shows all active tickets (result of report 1)
even without the TICKET_VIEW permission.

I think TicketBoxMacro should not list any tickets if the user does not have the right permissions.

I'm using the macro from this link: http://trac-hacks.org/svn/ticketboxmacro/TicketBox.py",Dalton Barreto
4910,Introduce option to limit number of tickets shown,enhancement,0.11,Shun-ichi Goto,new,2009-04-10T00:00:43+02:00,2009-04-10T00:00:43+02:00,"When generating a list of tickets to work on, I'd like to be able to list only a top number of them and then maybe have a link to the full report showing me all tickets matching a query.

In the special case, I'm using [wiki:UserPagePlugin User pages] which should show the most important tickets to work on for a user, but only maximum 10. I have a `[[TicketQuery]]` embedded for that at the moment, but TicketBoxMacro is more flexible, so I'd like to switch maybe. If I could limit the number of results shown in a !TicketBox, that is  ;-)",kontakt@…
5394,Dynamic variables support broken,defect,0.11,Shun-ichi Goto,new,2009-06-18T17:13:19+02:00,2009-06-18T17:13:19+02:00,"Seems that dynamic variable support has been broken ever since r4088.  The code that parses the dynamic variables out of the macro arguments was removed, and never replaced.  Now it just seems to expect to get values from dynamic variables from `req.args`, which doesn't make sense in the case of the macro.",Erik M. Bray
6724,Showing the ticket's owner,enhancement,0.11,Shun-ichi Goto,new,2010-02-24T21:33:50+01:00,2010-02-24T21:33:50+01:00,I'd like showing the ticket's owner like the summary is presented.,maxwellfarias@…
8775,Show files and logs of change sets in the ticket,defect,0.12,Shun-ichi Goto,new,2011-05-09T00:58:56+02:00,2011-05-09T00:58:56+02:00,"I just add some codes to show all tickets modified today. Some ones may be like this patch.

Usage like TicketBox except the ticket number.

For example:
{{{
TicketToday(summary,inline)
}}}",Bangyou Zheng
12323,Plugin has no license,task,,Shun-ichi Goto,new,2015-05-15T23:10:08+02:00,2015-06-03T21:44:19+02:00,The plugin currently does not indicate a license. Would you kindly add one? Suggested changes can be found in DevGuide#License.,figaro
4909,[PATCH] Add class documentation to appear in [[WikiMacros]] call,enhancement,0.11,Shun-ichi Goto,new,2009-04-09T23:40:10+02:00,2009-04-09T23:43:41+02:00,"As my users are ancouraged to make use of all the TracWiki magic they want to express themselves, I like to have all those possibilities well documented. However, when I looked at the WikiMacros Page after having installed TicketBoxMacro, I noticed that `[[TicketBox]]` only had the word ""None"" showing up as documentation.

So I did a little hacking and basically just copied the doc lines from the beginning of TicketBox.py to just after the class definition, so it gets rendered by a `[[WikiMacros]]` call.

I've svn-diffed it and attached it as a patch, though it's trivial after all. If you decide to use it, please remember to change all two instances of the documentation when you change sth therein. (Maybe one could put it in a variable to re-use it, but I'm all new to python as of now.)",kontakt@…