How to use BARD Tracker
Advanced Search
Overview
The Search field at the top right of your project panels finds tickets that match the search terms you enter.
Enter your search terms in the Search field and press Return. Use quotes around your search term to search for an exact phrase, or to search for terms containing spaces, dashes, underscores, or parentheses. This wil return tickets with matching text in the following fields:
- Ticket ID
- Title
- Description
- Comments
- Attachment filenames
Click the Locate button to open the original ticket.
Keywords
When viewing a project's tickets, you can search for tickets that match certain text strings and values for different fields.
- Keyword
- Example
- Description
- requester
- requester:HP
Returns tickets requested by the specified user.
Accepts: Initials, username, or full name with quotes.- owner
- owner:"Harry Potter"
Returns tickets owned by the specified user. TIP: You can also click a person's initials in a collapsed ticket.
Accepts: Initials, username, or full name with quotes.- reviewer
- reviewer:Hermione
Returns tickets containing reviews where the specified user has been assigned as the Reviewer.
Accepts: Initials, username, or full name with quotes.- my_work
- my_work:Voldemort
Show in-progress work for a given username (similar to the "My Work" panel, but for any user).
Accepts: Initials, username, or full name with quotes.- label
- label:"magic wands"
Returns tickets labeled with the matching text. TIP: You can also click a labels and epics in a collapsed ticket.
Accepts: Text, quoted if its multi-word.- has
- has:attachment
Returns tickets matching the specified condition.
Accepts: attachment, blocker, blocking, label, labels
Examples: has:attachment (tickets with file attachments), has:blocker (tickets that are blocked), has:blocking (tickets blocking others), has:label (tickets with any labels)- pivotal_id
- pivotal_id:123456
Find a ticket with a particular ID from your Pivotal Tracker imports.
Accepts: Pivotal Tracker ID number.- type
- type:feature,bug
Returns tickets of the specified type(s). Supports comma-separated values for multiple types.
Accepts: feature, bug, chore, release (case-insensitive)
Examples: type:feature, type:bug,chore, type:"feature, bug"- state
- state:started,finished
Returns tickets in the specified state(s). Supports comma-separated values for multiple states.
Accepts: unscheduled, unstarted, started, finished, delivered, rejected, accepted (case-insensitive)
Examples: state:started, state:finished,delivered, state:"started, finished"- name
- name:authentication
Returns tickets with titles matching the specified text (case-insensitive partial match).
Accepts: Any text string
Examples: name:login, name:bug, name:"user auth"- id
- id:12345
Returns the ticket with the specified ID.
Accepts: Numeric ticket ID
Example: id:54321- estimate
- estimate:1,2
Returns tickets with the specified story point estimate(s). Supports comma-separated values. Use "-1" (with quotes) for unestimated tickets.
Accepts: Point values, "-1" for unestimated
Examples: estimate:1, estimate:1,2,3, estimate:"-1", estimate:"1,-1"- epic
- epic:Authentication
Returns tickets associated with the specified epic (by partial epic title match). Finds tickets that share labels/tags with the epic.
Accepts: Epic title or partial title
Examples: epic:Authentication, epic:Payment- is
- is:blocked
Returns tickets with the specified status.
Accepts: blocked, blocking
Examples: is:blocked, is:blocking- accepted
- accepted:2025-03-30
Returns tickets accepted on the specified date. Supports ranges, comparison operators, and relative dates.
Accepts: YYYY-MM-DD, MM/DD/YYYY, date1..date2, >date,
Aliases: accepted_at, accepted_on, accepted_before, accepted_after, accepted_since- created
- created:>2025-01-01
Returns tickets created on or after the specified date. Supports ranges, comparison operators, and relative dates.
Accepts: YYYY-MM-DD, MM/DD/YYYY, date1..date2, >date,
Aliases: created_at, created_on, created_before, created_after, created_since- updated
- updated:"-1w"
Returns tickets updated on or after the specified date. Supports ranges, comparison operators, and relative dates.
Accepts: YYYY-MM-DD, MM/DD/YYYY, date1..date2, >date,
Aliases: updated_at, updated_on, updated_before, updated_after, updated_since
Combination and Negation
- Concept
- Example
- Description
- Combination
- requester:"Ron Weasley" owner:"Harry Potter"
You can combine multiple keyword clauses to find tickets that match all of the specified criteria.
- Negation
- -owner:hpotter
You can prefix a clause with a minus sign to negate it. In the example case, returning all tickets that are NOT owned by Harry Potter.