Creates a new BugzillaContext, suitable for connecting to the provided server. You should try to reuse BugzillaContexts whenever possible, because creating them is expensive.

Attempts to create a logged-in BugzillaSession using the provided username and password. Returns Nothing if login fails.

Creates a BugzillaSession using the provided api key.

Creates an anonymous BugzillaSession. Note that some content will be hidden by Bugzilla when you make queries in this state.

Holds information about a BugzillaServer and manages outgoing connections. You can use newBugzillaContext to create one.

A session for Bugzilla queries. Use anonymousSession and loginSession, as appropriate, to create one.

Searches Bugzilla and returns a list of Bugs. The SearchExpression can be constructed conveniently using the operators in Web.Bugzilla.Search.

Similar to searchBugs, but return _all fields.

Like searchBugs, but returns a list of BugIds. You can retrieve the Bug for each BugId using getBug. The combination of searchBugs' and getBug is much less efficient than searchBugs. searchBugs' is suitable for cases where you won't need to call getBug most of the time - for example, polling to determine whether the set of bugs returned by a query has changed.

Search Bugzilla and returns a limited number of results. You can call this repeatedly and use offset to retrieve the results of a large query incrementally. Note that most Bugzillas won't return all of the results for a very large query by default, but you can request this by calling searchBugsWithLimit with 0 for the limit.

Similar to searchBugsWithLimit, but return _all fields.

Like searchBugsWithLimit, but returns a list of BugIds. See searchBugs' for more discussion.

Retrieve a bug by bug number.

Retrieve all bug field by bug number

Retrieve a bug by attachment number.

Get all attachments for a bug.

Get all comments for a bug.

Get the history for a bug.

Search user names and emails using a substring search.

Get a user by email.

Get a user by user ID.

All information on how to connect to a host and what should be sent in the HTTP request.

If you simply wish to download from a URL, see parseRequest.

The constructor for this data type is not exposed. Instead, you should use either the defaultRequest value, or parseRequest to construct from a URL, and then use the records below to make modifications. This approach allows http-client to add configuration options without breaking backwards compatibility.

For example, to construct a POST request, you could do something like:

initReq <- parseRequest "http://www.example.com/path"
let req = initReq
            { method = "POST"
            }

For more information, please see http://www.yesodweb.com/book/settings-types.

Since 0.1.0

A field which you can search by using searchBugs or track changes to using getHistory. To get a human-readable name for a field, use fieldName.

A Bugzilla user.

Flags, which may be set on an attachment or on a bug directly.

A Bugzilla bug.

An external bug.

An external bug type

An attachment to a bug.

A bug comment. To display these the way Bugzilla does, you'll need to call getUser and use the userRealName for each user.

History information for a bug.

An event in a bug's history.

A single change which is part of an event. Different constructors are used according to the type of the field. The Modification describes the value of the field before and after the change.

A description of how a field changed during a HistoryEvent.

Provides a human-readable name for a Field.