> For the complete documentation index, see [llms.txt](https://docs.toolsplus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toolsplus.io/atlassian-cloud/travis-for-jira/getting-started.md).

# Getting Started

## 1. Installation

Log into your Jira instance as an admin. The click **Jira Settings > Apps > Find new apps**. The Find new apps screen loads.

Use the search box to locate **Travis for Jira** and click **Free trial** to get started.

## 2. Configure Travis CI to report build information

After successful installation, edit your `.travis.yaml` file/s to make Travis CI report your build information to your Jira instance.

From your Jira home page go **Jira Settings > Apps** and then select **Configure** under the Travis for Jira section.

![](/files/-LZ3i7A8dNfKxB2ftLYq)

Copy the snippet and paste it in your `.travis.yaml` file. You can use the same snippet for all your GitHub repositories that you would like to send Travis CI build information to Jira.

## 3. Associate builds to Jira issues

Once you have updated your `.travis.yaml` start using [smart commits](https://confluence.atlassian.com/fisheye/using-smart-commits-960155400.html) in your Git commit messages or include the Jira issue in the Git branch names to associate a Travis CI build with a Jira issue.

{% hint style="info" %}
If you are using **GitHub for Jira app** you are required to wrap the issue key in angular brackets in your commit message, e.g. `[TFJ-1] A commit message`. Travis for Jira does not impose this requirement but we are perfectly fine do wrap your issue keys.
{% endhint %}

When Travis CI tells the app about a new build it will try to extract one or more issues keys from the branch name or commit message and associate the build with those issues.

:tada: That's it, get productive and start releasing with confidence :sunglasses: