How to use BARD Tracker
Adding Tickets
Adding new tickets
To create a new ticket in the Todo, Icebox or an Epic Tickets panel, click the + ADD TICKET button at the top of the panel.
Alternatively, you can press the A key to add a new ticket to the top of the Icebox. Epic panels also have a + ADD TICKET button for adding tickets with that epic's label.
Clicking the + ADD TICKET button opens a draft ticket detail window in the appropriate panel.
Location of newly added tickets
By default, newly added tickets are placed at the top of the Icebox or Todo panels; above all other unstarted tickets.
If you'd prefer that new tickets be placed below all other existing tickets, there's an alternative + ADD TICKET TO BOTTOM button at the bottom of the Todo panel.
Ticket types
In the ticket title, type a brief description of its purpose that is appropriate to the ticket type. These are the four types of tickets in BARD Tracker:
Features
Features are the default ticket. Features are tickets that provide verifiable business value to the team's customer (e.g., “Add a Special Instructions field to the checkout page,” “As a shopper, I want to see my purchase hiticket load in half a second so that I can find previously purchased items,” or “Add a new method addToInventory to the public API”). The delivery team gives each feature a ticket point estimate during iteration planning. Valid ticket states are unscheduled, unstarted, started, finished, delivered, accepted, or rejected.
Chores
Chores are tickets that are necessary but provide no direct, obvious value to the customer (e.g., “Update SSL Certs”). Because they don't typically require extra validation when they're finished, the states for chores are just unscheduled, unstarted, started, and accepted.
Bugs
Bugs represent unintended behavior that can be related to features (e.g., “Login box is wrong color” or “Price should be non-negative”). Bugs have the same states as features.
Releases
Releases are milestone markers that allow your team to track progress toward concrete goals (e.g., stakeholder or investor demos, software launches, etc.). It's possible to specify target dates for releases. All tickets for a milestone or release should go above the marker for it.
Filling in the details
Ticket title is the only required field, but you can add details in the Description.
New tickets are typically left unestimated until the delivery team meets to discuss them. Type in the Labels field to create a new label or choose an existing one.
When you add a ticket, you become the requester by default. You can set that to any project member by clicking on the drop-down menu to the right. Typically, feature tickets are requested by the product owner or someone else in a customer role, and that person will also do the final acceptance of the ticket. You don't need to assign an owner to the ticket at this point. When someone starts the ticket, they will be assigned as the default owner. A ticket can have multiple owners (e.g., a designer and a developer pair).
Click the Save button just below the ticket title when you have entered at least a ticket title. You can come back to a ticket and change any of its details later.
After saving the ticket, you can expand it again to see the ticket ID assigned to it. Note that the saved ticket now has a Collapse button.
If you are the ticket requester or an owner, you'll automatically follow that ticket, meaning that you'll get appropriate updates in your account email.
Following tickets
To make sure you receive notifications on specific tickets, select the Follow this ticket checkbox in the expanded view of a ticket. You will receive notification emails for all comments posted to tickets you follow. If you are the Requester or Owner of the ticket, you automatically follow it and the checkbox will be checked by default.
To have someone else follow a ticket, just @mention them in a comment on the ticket. See below for more about comments.
Comments and attachments
BARD Tracker facilitates discussions about a ticket through comments.
Anyone not already following a ticket becomes a follower when they add a comment. You can also @mention other project members, as well as yourself, to make them followers of the story and receive appropriate notifications. You can specify whether you receive email notifications and/or in-app notifications when comments are added to a story.
You can edit or delete comments you added yourself. Project owners can delete any comments.
To attach one or more items to a comment, click on the paperclip icon and select the type of attachment you want. This will open the appropriate dialog to select your attachment(s).