Immediately after installation, the add-on displays the TeamCity tab on the Project, Version and Issue pages in JIRA and starts indexing all TeamCity builds looking for those containing JIRA Issue Keys.
Issue Key is a JIRA issue ID. Normally, it's specified in a commit log message in a version control system integrated with TeamCity. For example, a developer commits a source code file adding the log message DEMO-5 Added compatibility with older browser versions, the build that includes this change will be shown in JIRA in the DEMO project and in issue DEMO-5.
While the plugin is analyzing the builds, you will see the the following message on the TeamCity tab.
This process may take a while on large instances. Also, please see here.
When the initial indexing is over, you will see all found builds on the TeamCity tab of the Project (shown below), Version and Issue pages.
If no relevant builds are found, you will see the message No associated builds are found. From now on, the plugin will update the build list in JIRA every 2 minutes.
If you see the message that no builds are available, please see this page to identify its cause.
Each issue in JIRA is assigned to a project and (optionally) to a version, therefore a build list displayed on the Project tab is compiled of the issues assigned to a given project, and a build list displayed on the Version tab is compiled of the issues assigned to a given version.
The TeamCity tab looks the same for issues, projects and versions. It contains the main build parameters, such as a start date, build duration, commit log, etc., and allows you to switch to TeamCity for detailed information.
You can filter builds by one of the following parameters:
- Build Period