Opened 16 years ago
Closed 16 years ago
#7399 closed defect (fixed)
TicketQuery macro does not follow default parameters as documented
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | normal | Milestone: | 0.11.1 |
Component: | ticket system | Version: | 0.11-stable |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Based on r7289 of 0.11-stable branch.
Documentation says:
The max parameter can be used to limit the number of tickets shown (defaults to 0, i.e. no maximum).
In my Trac, there is a limit to how many tickets are returned. Shown below is query and result (I use list format normally but chose compact to save space). Adding the parameter "max=0" does list the remainder of the tickets.
[[TicketQuery(status=closed,summary^=PPR,format=compact)]]
#66, #70, #71, #82, #84, #53, #54, #56, #57, #58, #59, #63, #83, #87, #130, #55, #65, #68, #69, #75, #76, #80, #86, #88, #90, #91, #92, #93, #94, #95, #96, #97, #98, #99, #101, #102, #103, #104, #105, #106, #107, #108, #109, #110, #111, #112, #113, #114, #115, #116, #117, #118, #121, #122, #123, #126, #127, #128, #129, #131, #132, #134, #135, #136, #137, #138, #139, #140, #144, #145, #146, #147, #148, #151, #153, #154, #157, #158, #159, #163, #164, #165, #166, #167, #168, #169, #170, #171, #174, #176, #177, #178, #181, #183, #184, #186, #189, #191, #195, #196
[[TicketQuery(status=closed,summary^=PPR,format=compact,max=0)]]
#66, #70, #71, #82, #84, #53, #54, #56, #57, #58, #59, #63, #83, #87, #130, #55, #65, #68, #69, #75, #76, #80, #86, #88, #90, #91, #92, #93, #94, #95, #96, #97, #98, #99, #101, #102, #103, #104, #105, #106, #107, #108, #109, #110, #111, #112, #113, #114, #115, #116, #117, #118, #121, #122, #123, #126, #127, #128, #129, #131, #132, #134, #135, #136, #137, #138, #139, #140, #144, #145, #146, #147, #148, #151, #153, #154, #157, #158, #159, #163, #164, #165, #166, #167, #168, #169, #170, #171, #174, #176, #177, #178, #181, #183, #184, #186, #189, #191, #195, #196, #201, #204, #210, #213, #214, #219, #224, #73, #74, #60, #61, #81, #179
Documentation says:
The order parameter sets the field used for ordering tickets (defaults to id).
The macro does not order by ID by default. Adding "order=id" does perform the ordering. I don't show the results here, but it is correct.
There are also other related tickets and changesets that did not seem to match this problem (or reported it as fixed but it isn't now:) [7184], [6908], #5793, [5149]…
Attachments (0)
Change History (2)
comment:1 by , 16 years ago
Owner: | set to |
---|
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
The default values are now those specified in the documentation, with [7292].
I'm looking at the issues.