Bug 1092880 – [Docs] [Technical] [async]max parameter needs better explanation and usage example

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1092880 - [Docs] [Technical] [async]max parameter needs better explanation and usage example

Summary:	[Docs] [Technical] [async]max parameter needs better explanation and usage ex...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	Documentation (Show other bugs)
Sub Component:
Version:	3.4.0
Hardware:	Unspecified Unspecified

Priority	high Severity unspecified
Target Milestone:	---
Target Release:	3.5.0
Assigned To:	Andrew Burden
QA Contact:	Ruediger Landmann
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2014-04-30 03:44 EDT by Andrew Burden
Modified:	2015-02-15 23:47 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-02-15 23:47:01 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrew Burden 2014-04-30 03:44:47 EDT

Luca Villa wrote:
the use of the max= parameter to influence the number of results when the default number of 100 is insufficient should be also mentioned/duplicated on the pagination section as they seem to be strictly related.
A usage example would be even better.

Note You need to log in before you can comment on or make changes to this bug.