Check out our new app for Confluence Smart Attachments. Store your project documents, artifacts, and media assets in the shareable space storage in Confluence.
Page tree
Skip to end of metadata
Go to start of metadata

This feature is available for JIRA Server only.

Starting from version 2.4.0, TeamCity Integration for JIRA add-on allows you to track the build number for fixed issues. It allows you to define the build that fixes the issue or adds the feature reported in the JIRA issue.

Before proceeding to configuration of this custom field, please refer to the documentation about management of custom fields in JIRA.

Adding a Custom Field

  1. Navigate to JIRA Administration > Issues > Fields > Custom Fields.
  2. Click Add Custom Field.
  3. In the Select a Field Type form, switch to view all custom fields and enter 'TeamCity' into the search field.
  4. Select TeamCity Fixed in Build field.
  5. Click Next.
  6. Specify the field name and its description.
  7. Click Create.
  8. Select the screens where you want to display this field.
  9. Save the configuration.

Configuring the Custom Field

  1. Locate the newly added custom field and click the cogwheel button.
  2. Click Configure.
  3. On the opened page, click Edit Default Value.
  4. Here define the parameters for population of the Fixed in build field with the relevant builds, as follows:
    1. Selection Criteria - choose the appropriate way of selecting builds, as follows:
      1. Single build (one against multiple build configurations).
      2. Multiple builds (one against each build configuration).
    2. Build Tracking - select the appropriate option for populating the Fixed in Build field, as follows:
      1. Most recent build (successful or failed) - the add-on populates the field automatically with the number of the recent successful or failed build.
      2. Most recent successful build - the add-on populates the field automatically with the number of the recent successful build number.
      3. First successful build - the add-on populates the field automatically with the number of the first successful build.
      4. First build (successful or failed) - the add-on populates the field automatically with the number of the first successful or failed build.
      5. Manual - the user can select the appropriate build number.The build number is not assigned automatically if using this option.
  5. Add one or multiple builds configurations for the field population.
  6. .Click Set Default.

Once you have configured and added the custom field, you can get the field populated with the number of the build that fixes the issue or adds the requested feature.

To delete the no longer used build configuration, click the Delete  icon

  • No labels