How to use BARD Tracker
Git Integration
We currently support integrating with GitHub and Gitea, two popular git-based code collaboration platforms. This integration allows you to link your BARD Tracker tickets with your git repositories, enabling automatic lifecycle updates and activity tracking based on your git actions.
Click the INTEGRATIONS tab in your project view to get started!
If your organization uses another git-based code collaboration platform such as GitLab or Bitbucket, please submit a feedback ticket or email us at info@bardtracker.com, and we'll add support for it.
Branches
If you push a branch that contains the ticket id, BARD Tracker will automatically attach the branch to the ticket. For example, creating a branch with the name 123456-new_feature or feature/123456_new_feature will attach it to the ticket with id 123456.
Pull Requests
BARD Tracker will automatically attach a pull request to a ticket if the PR's branch name starts with that ticket's ID, as described in the Branches section above. The PR icon color will match its status: Open, Close, or Merged.
Commits and Ticket State Changes
Any commits in a linked branch will be added to that ticket's activity/comment stream.
For commits not in a linked branch, you can still add them to a ticket's activity/comment stream by tagging the ticket ID in the commit message. Add the Tracker ticket id with a preceding hash symbol within square brackets at the end of your commit message.
You can optionally include a state change for the Tracker ticket within the brackets. Currently, there are two state changes supported: Finished and Delivered. For example, including “Finishes”, “Fixes”, or “Completes” in your commit message will change the specified ticket to the Finished state, while “Delivers” will change the specified ticket to Delivered state. These words can be in the past tense as well.
[(Finishes|Fixes|Completes|Delivers) #TRACKER_TICKET_ID]The commit message in the example below adds a commit to ticket 123123 and changes ticket state to “Finished” with the “finishes” keyword.
git commit -m "[finishes #123123] Updated settings for flux capacitor"You can specify multiple ticket ids in a commit by separating each id with a comma or space, within square brackets. However, all ticket ids will show in the commit on all specified stories.
[#TRACKER_TICKET_ID,#TRACKER_TICKET_ID] or [#TRACKER_TICKET_ID #TRACKER_TICKET_ID]Alternatively, you can place each ticket id in its on set of square brackets, and separate each set of brackets with a comma or space. This will prevent ticket ids from showing up in non-related stories.
[#TRACKER_TICKET_ID],[#TRACKER_TICKET_ID] or [#TRACKER_TICKET_ID] [#TRACKER_TICKET_ID]