![]() ![]() Note that a user specified in the connection to Jira should have sufficient permissions to view Jira issues. TeamCity will detect newly created projects in Jira and automatically synchronize the list of project keys. If the connection is successful, the Project Keys field will be automatically populated. You can also load all project keys automatically: enable Use all Jira projects automatically and test the connection to your Jira server. For example, if a project key is WEB, an issue key like WEB-101, mentioned in a VCS comment, will be turned into a link to the corresponding issue. TEAMCITY JIRA INTEGRATION PASSWORDĪ username for self-managed Jira (specified in the Jira user profile) or email for Jira Cloud.Ī password for self-managed Jira or API token for Jira Cloud.Įnter a space-separated list of project keys to specify which strings should be recognized as references to issues in Jira. Specify the connection name to distinguish it from the other connections.Įnter the base URL of your Jira instance or server. To enable the integration, create a connection to Jira on the Project Settings | Issue Trackers page and specify the following settings: If the settings are different in a subproject, they have priority over the parent project's settings. Note that enabling integration for a project enables it for all its subprojects as well. TeamCity updates statuses of Jira issues displayed for builds every 10 minutes or when new commits are detected.Įnabling TeamCity integration with Jira requires Project Administrator permissions as it is configured at a project level. Mark fixed issues as Resolved in Jira to display them with the Fixed status in TeamCity logs (the time of resolve does not really matter). When committing changes to your version control, always mention the issue key related to the fix in the comment to the commit. You can filter the list to a particular range of builds and/or enable the Show only resolved issues option to display only issues fixed in the builds.įollow these recommendations to get the maximum benefit from the Jira integration: To view issues related to a whole build configuration (not only to individual builds), use the Issue Log tab of the Build Configuration Home page. Issues fixed in the build can be viewed on the Issues tab of the build results: To see the basic details of an issue in the TeamCity UI, open the Changes tab of the related build’s results and hover over the icon next to the issue key: It transforms these keys into links to the corresponding issues in Jira and displays them to TeamCity users in the UI. When integration with Jira is enabled, TeamCity automatically detects Jira issue keys mentioned in the comments of VCS commits. Displaying Links to Jira Issues in TeamCity UI TEAMCITY JIRA INTEGRATION HOW TOThis article describes how TeamCity behaves when integrated with Jira and contains instructions on how to enable and configure the integration. Reporting TeamCity build statuses to Jira Cloud. View is simple, right now its role is just to display data without any links to Jira issues in the TeamCity UI - applicable to self-managed Jira (Data Center and Server 4.4 or later) and Jira Cloud. Ok, let’s start with the code, first IJiraClient – interface, that RestEase library uses as an abstraction to connect to REST API endpoint:ĪuthenticationHeaderValue Authorization ) Given that, my plan at the moment is to do the simplest view where I display scrum board and issues from current sprint grouped by status. Workflow – describes available statuses and transitions between them.Status – all issues need to have status in which they are, most popular – To Do, In Progress, Testing, Done.Sprint – in Scrum clearly defined period (usually two weeks) to organize team’s work.Board – used to view actively developed issues, can be either Scrum or Kanban.Issue – a task, bug, improvement attached to project.JIRA data model consists of several entities: Recommended is OAuth, but for now, I’ll use basic HTTP authentication, because at the moment the priority is just to connect and display issues from JIRA. Same as with TeamCity integration I’ll leverage the power of REST API and RestEase library. For authentication, you have two options – basic HTTP authentication and oath. Documentation is straightforward, so It was easy for me to do it. JIRA is one of the most popular tools for IT teams to manage work and it’ll be next integration for TeamScreen. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |