Minor improvements.

New in this release

• Added the resolving of the the $JIRA_KEY variable in the build comment when triggering a build in TeamCity through the post-function in Jira.

New in this release

• Added the resolving of the the $JIRA_KEY variable in the build comment when triggering a build in TeamCity through the post-function in Jira.

Fixed in this release

• Resolved the issue with resolving the $JIRA_KEY variable in the build comment when triggering a build in Jira through the TeamCity Build Runner field.

Fixed in this release

• Resolved the issue with resolving the $JIRA_KEY variable in the build comment when triggering a build in Jira through the TeamCity Build Runner field.

New in this release:

• Added support for Jira 8.0.

Fixed in this release

• Resolved the issue with display of the canceled builds in the TeamCity Activity gadget.

Fixed in this release

• Resolved the issue with display of builds on the TeamCity tab when Jira uses the MSSQL database.

Updates in the build indexing mechanism require the complete re-indexation of your TeamCity data.

New in this release:

• JQL query to search for issues that relate to a specific build. Now you can instantly find all the issues that pertain to a specific build by entering the corresponding JQL query.
• JQL query to search for issues against the build number which fixes the issue or against the build status (failure or success). Now you can show only issues with the the successful or failed build status, so that you can view only the relevant information.

The new version of add-on also includes the following features:

• Added the mechanism for storing build-specific information for improving performance of showing it in issues.
• Default indexation depth is limited to 365 days.

Fixed in this release:

• Resolved the issue with showing the warning 'The server is unavailable. Please verify the settings of the connection.' when none builds are indexed.

Read more.

The new version of the app includes the following features:

• Optimized response of UI elements and data queries that improved performance and data loading on the TeamCity tabs and in gadgets.
• Unified the date format used across the app sections. Now the app relies on the date format defined in the Jira settings and shows all the dates accordingly.

Fixed in this release:

• Resolved the issue with display of build data when opening the Teamcity tab for a specific issue in the Issue Navigator view.

The Fixed in build field gets support for multiple build configurations:

• Now you can define multiple build configurations for selecting one or multiple builds from different configurations.
• Added output of the number of the build which addresses the issue on the Scrum and Kanban board cards.
• Now you can quickly view the number of the build while viewing the development progress in Issue Navigator.

Read more

Fixed in this release:

• Resolved the issue with operation of the Teamcity Build Configuration gadget on the Jira dashboard.

Fixed in this release:

• Resolved the issue with loading Jira issues upon the unavailability of the TeamCity server when there is the Fixed in Build field on the screen.
• Restored the message shown in the Builds history form when there have been no builds triggered from Jira for the current issue.

Updated the look of the TeamCity Build Configurations gadget:

• Now the TeamCity Build Configurations gadget shows builds from different branches that are managed by the specific build configuration. You can also select the appropriate branch when you trigger a new build from the gadget.

Option to select the appropriate branch when triggering a new build:

• Now you can select the appropriate branch when triggering a new build through the TeamCity Build Runner field.

Read more.

The new version of add-on includes the following features:

• Added support for composite builds
• Improved indexation of queued builds after completion of initial build indexation

Fixed in this release:

• Resolved the issue with editing configuration of the TeamCity Build Runner field when changing ID of the build configuration in TeamCity

Fixed in this release:

• Resolved the issue with disappearance of the build status icons when switching between tabs on the Releases page.
• Resolved the issue with occurrence of NPE error upon the initial indexation of TeamCity build data with the enabled Index Depth option and builds in the queue.

Fixed in this release:

• Resolved the issue with the Out of Memory error when viewing build data on the TeamCity tab by a great number of users in projects with more than 200K indexed builds.
• Resolved the issue with the page load timeout when viewing the Release hub page for version releases with more than 500 issues.

The new version of add-on includes the following features:

• Updated the link in the Getting Started form which is displayed after installation or update of the app. Now it points to the TeamCity Servers section.
• Added the Reset all filters link which is displayed after filtration of builds if no builds matching the filtration criteria are found.

Fixed in this release:

• Resolved the issue with writing a warning into Jira log file upon opening the dashboard with the Activity Stream gadget.

Added the on-boarding wizard that appears after the first add-on installation in Jira:

• Now you can quickly learn about add-on capabilities and set up integration with your TeamCity server.

The new version of add-on also includes the following features:

• Added one decimal place for indicating the indexation progress in the Troubleshooting section.

Fixed in this release:

• Resolved the issue with editing the access credentials (login and password) for the saved TeamCity server.
• Resolved the issue with using the old access credentials for the re-created application link pointing to the same TeamCity server.
• Resolved the issue with indexation of queued builds when changing the order of their running in TeamCity.

This version is compatible with TeamCity 9.1+.

The new version of add-on includes the following features:

• Improved indexation of the queued builds and added a mechanism that skips builds that were removed in TeamCity.

Fixed in this release:

• Resolved the issue with abnormal memory consumption. The issue occurred on TeamCity instances with a great number of builds when opening the project view in Jira.

Integrated the add-on with Release Hub:

• Now you can instantly view the essential build information for all issues within the release.

Added the post-function that triggers build execution upon issue transition from one status to another:

• Now you can automatically run builds in your TeamCity when you perform the issue transition to the specific status.

Added a capability to view the builds for a custom period:

• Now you can easily define the start and end dates for build filtration in the project and issue views.

The new version of add-on also includes the following features:

• Added display of the successfully passed and failed tests when viewing build information in Release Hub.

Fixed in this release:

• Resolved the issue with triggering builds through the TeamCity Build Runner field in TeamCity 2017.x. Additional configuration of TeamCity is required, please see our FAQ.

Read more

The new version of add-on includes the following features:

• Increased the delay for hiding the section with build changes after removing the focus from the section while moving the mouse pointer.
• Changed the way of displaying the build duration for the builds created within less than a second. Now they are displayed as '< 1s' instead of '0s'.

Fixed in this release:

• Resolved the markup issue with the column overlapping on small screens (13" and less) when viewing the TeamCity section in the project view with the expanded sidebar.

Improved the way of creating application links to TeamCity servers:

• Now you can much more quickly create application links to TeamCity servers.

Improved the display of multi-level projects when filtering builds, configuring gadgets and custom fields:

• Now you can better navigate across multi-level projects and select only the ones you need.

Fixed in this release:

• Resolved the issue with the persistent display of the message about the ongoing indexation when there are no builds on TeamCity server.
• Corrected the mechanism of caching related builds and resolved the issue with the incorrect parsing of issue keys after modifications on TeamCity servers.

☞ Read more

Added a capability to define the issue key property when triggering a build from Jira:

• Now you can specify the property that passes the issue key to TeamCity when you trigger the build remotely from Jira.

The new version of add-on also includes the following features:

• Added a capability to enter or modify the comment appended to the build.
• Added tracking of users and build numbers set in the Fixed in Build custom field on the History tab of the issue view.
• Added the flag indication of the build set in the Fixed in Build custom field.

Fixed in this release:

• Resolved the issue with manual selection of the build number for populating the Fixed in Build field in one issue and causing the reset of the automatic field population to the manual mode for all issues within the project.

Read more.

Improved display of the great number of related issues:

• Now you can expand and collapse the list with multiple related issues when viewing build activity.

Fixed in this release:

• Resolved the issue with showing builds automatically cancelled by TeamCity in the Teamcity Activity gadget.
• Corrected behavior of showing the TeamCity Activity gadget when there are no more builds in the build activity stream. The following message is displayed 'No more builds'.

Added the custom field allowing you to manually or automatically indicate the number of build fixing the issue:

• Now you can automatically get the number of build adding the requested feature or fixing the reported issue or populate it manually.
• You can also define the appropriate way of populating the field with the number of the build that fixes the issue.

The new version of add-on also includes the following features:

• Changed the icon for remote build triggering through the TeamCity Build Configurations gadget.
• Added the TeamCity section into the project view of Jira. Prior to this, the TeamCity section was displayed in the Add-ons section of the project view.
• Added a capability to sort build configurations in the TeamCity Build Configurations gadget.

Fixed in this release

• Resolved the issue with incomplete data indexation of builds being in a queue for a long time.

Read more.

Fixed in this release:

• Resolved the issue with incomplete data indexation of builds being in a queue for a long time.

Fixed in this release:

• Resolved the issue with showing additional projects (besides the selected projects) in TeamCity Activity gadget with the set build period.

Fixed in this release:

• Resolved the issue with showing additional projects (besides the selected projects) in TeamCity Activity gadget with the set build period.

Fixed in this release:

• Resolved the issue with the failure of data indexation after removal of the build in TeamCity 9+.

Fixed in this release:

• Resolved the issue with the failure of data indexation after removal of the build in TeamCity 9+.

Fixed in this release:

• Resolved the issue with the incorrectly working build filters in the issue and project views.

Fixed in this release:

• Resolved the issue with the incorrectly working build filters in the issue and project views in Jira 6.4.12.

Added the TeamCity Build Configurations gadget that you can display on the Jira dashboard:

• Now you can instantly view the recently completed builds, their status and duration. Additionally, you can remotely trigger builds on TeamCity server and seamlessly transition to TeamCity to view details on the recent builds of the specific build configuration. For details, see this page.

The new version of add-on also includes the following features:

• Added a capability to reindex data for each TeamCity server independently.
• Added display of data indexation percentage for each TeamCity server individually.
• Added output of the project on the TeamCity tab for individual builds related to the currently opened Jira issue.

Learn more.

Added a capability to remotely trigger builds on TeamCity server from Jira:

• Now you can instantly and directly run builds while viewing Jira issues.You need to add a custom field into the related screens and set its configuration. Then you can remotely run builds in TeamCity from Jira and view history of builds that were run from Jira.

The new version of add-on also includes the following features:

• Added display of the TeamCity tab in Service Desk projects.

Fixed in this release:

• Resolved the issue with the continuously refreshed data when opening the TeamCity tab with the expired license for the add-on.

Added compatibility with Jira 7.

Now you can continue viewing TeamCity build data in the new Jira 7. For the details on the required procedures to perform while migrating from Jira 6 to Jira 7, see our FAQ.

New in this release:

• Added support for Jira 6.4.10.

New in this release:

• Optimized the initial data indexation and added validation of the initially indexed builds. If no build data has been indexed due to some issues with permissions or connectivity, the add-on launches a repeated initial data indexation.

Fixed in this release:

• Resolved the issue with showing no application link names on the dedicated tabs if more than one application link is registered.
• Added exclusuion of the root project when showing the list of projects from the multi-level project.
• Resolved the issue with non-update of the URL in the address line after removing some filtering options.
• Resolved the issue with showing no related projects in the Project filter.

Fixed in this release:

• Resolved the issue with showing no TeamCity build data on the TeamCity tab in the issue if this tab was active when the user transitioned to a new issue.

New in this release:

• TeamCity integration for Jira add-on works with TeamCity 8.1+ and Jira 6.1+.
• Added a capability to show TeamCity Activity gadget on the Jira dashboard. Now you can easily track the build activity on your TeamCity server and quickly access the related information.
• Added the set of filters to narrow the range of builds matching the definite criteria. Now you can instantly filter builds by status, build period, agent or project while viewing Jira issues or the overall project.

The new version of the add-on also includes the following:

• Added output of the build configuration and branch name if the build was created from the featured branch.

Learn more.

New in this release:

• Added support for Jira 6.4.

New in this release:

• Added support for TeamCity 9.0.

Fixed in this release:

• The first 10 VCS changes are shown on TeamCity tab. You can view all changes directly at TeamCity clicking by "View all changes" button if build contains bigger number of changes.

Fixed in this release:

• Resolved the issue when version 1.7.3 fails to start if Jira is connected to Oracle database.

New in this release:

• The add-on has received support for Jira Data Center. Now you can integrate your Jira Data Center with multiple TeamCity servers for greater flexibility and outstanding performance.

The new version of add-on also includes the following feature:

• Added the Response Size option for limiting maximal response size from TeamCity.

Fixed in this release:

• Resolved the issue with personal builds causing errors during indexation of TeamCity data.
• Corrected the way of loading builds on the dedicated tabs when scrolling down the list of builds.

Upgrade is strongly recommended for users who have already installed the version 1.7.1. Read the version 1.7.1 release notes in order to get more information about new shiny features.

New in this release:

• Compatibility with Jira 6.3

Fixed in this release:

• Fixed a problem when the add-on could persist duplicated records in the database during the indexing process.

The add-on has received support for multilple TeamCity servers:

• The add-on allows you to add as many as needed TeamCity servers and keep an eye on all your projects, builds and agents at once.

The new version of add-on also includes the following features:

• Added output of information about start time of data indexing on the Troubleshooting page;
• Added output of percentage of data indexing on the Troubleshooting page.

Read the TeamCity Integration for Jira 1.7.0 release notes.

StiltSoft is happy to announce the release of TeamCity Integration for Jira version 1.6.1

What's New

This is a must-have update for version 1.6.0 that has a buggy support for TeamCity 8.

Also, please, note that the plugin is dual licensed now and existing customers can get the Paid Update Available message in Confluence Administration that should be ignored. Please read more in our blog.

Changes Overview

Starting from version 1.6.0 this plugin will be available for buying at Atlassian Marketplace as well as on our website. All licenses previously bought on our website are being imported to Marketplace.

When you update the plugin in the Jira Administration Console, you'll see a notification about an available paid update.

What you should, if you purchased your license

less than a year ago:

1. Click Paid Update. We're neither charging you for this update nor changing your license period!
2. When the plugin is updated, ignore the Get License dialog and UPM notifications saying that no license is found. The plugin is still up and running.
3. (Optional) To get rid of UPM notifications, install the Marketplace license as soon as we migrate it.

more than a year ago:

1. Wait till your license is migrated to Marketplace.
2. Renew the license at Marketplace

How will your license be migrated?

If the email used for buying the license on our website is different from that used in your account at my.atlassian.com, a new account with this email will be automatically created. Otherwise, you will just see the plugin license in your Atlassian account.

StiltSoft is happy to announce the release of Jira TeamCity Plugin version 1.5.3

What's new

• If your Jira and TeamCity both are located behind a proxy and your proxy prohibits connections from Jira to TeamCity, please, add option -DdisableProxyForTeamcity=true to your JVM

StiltSoft is happy to announce the release of Jira TeamCity Plugin version 1.5.2

What's new

• Compatibility with TeamCity 8

StiltSoft is happy to announce the release of Jira TeamCity Add-on version 1.5.1.

Bugs fixed

StiltSoft is happy to announce the release of Jira TeamCity Add-on version 1.5.0.

What's new

• Introducing support for Atlassian Jira 6.0

In this release we are aiming to improve diagnostic of TeamCity connectivity:

• During initial indexing of builds you can see percent of indexing completeness.
• Option to restart indexing manually
• All errors raised when requesting data from TeamCity are logged and counted now at the plugin administration page.
• New option to skip builds which can not be received from TeamCity due to any errors (network errors, TeamCity integrity errors). Caution: please enable this option only if you have permanent problems with TeamCity connectivity and initial indexing won't complete.

Also there are some compatibility changes:

• The plugin is compatible with brand new Jira 5.2!
• Compatibility with TeamCity 6.0 was repaired.
• Warning: This is the last major update which is compatible with Jira 4.4. Next major update of the plugin will be compatible only with Jira 5.0+.

In this release we are aiming to improve diagnostic of TeamCity connectivity:

• During initial indexing of builds you can see percent of indexing completeness.
• Option to restart indexing manually
• All errors raised when requesting data from TeamCity are logged and counted now at the plugin administration page.
• New option to skip builds which can not be received from TeamCity due to any errors (network errors, TeamCity integrity errors). Caution: please enable this option only if you have permanent problems with TeamCity connectivity and initial indexing won't complete.

Also there are some compatibility changes:

• The plugin is compatible with brand new Jira 5.2!
• Compatibility with 6.0 was repaired.
• Warning: This is the last major update which is compatible with Jira 4.4. Next major update of the plugin will be compatible only with Jira 5.0+.

• TeamCity tab for project version was added
• TeamCity tabs are shown to users having View Version Control / View Issue Source Tab
  Permission

Fixed error in case when there are no builds in TeamCity or very first build is unfinished

Fixed error in case when there are no builds in TeamCity or very first build is unfinished

• Now you can see every build related to issue or project, not only 25 newest. Just scroll page down and older builds will be displayed automatically!
• Caching mechanism was improved and speed of TeamCity tabs generation increased.

• Now you can see every build related to issue or project, not only 25 newest. Just scroll page down and older builds will be displayed automatically!
• Caching mechanism was improved and speed of TeamCity tabs generation increased.

• The plugin displays full name of TeamCity user if applicable
• Some small UI fixes

• The plugin displays full name of TeamCity user if applicable
• Some small UI fixes

Minor fixes for TeamCity gadget

Minor fixes for TeamCity gadget

Bunch of small UI improvements

Bunch of small UI improvements

Link to file changes in TeamCity was fixed

Link to file changes in TeamCity was fixed

Link to evaluation license in administration console was broken in some cases

Link to evaluation license in administration console was broken in some cases

Some fixes for free licenses

Some fixes for free licenses