Configuring JIRA DVCS Connector Plugin at a project level

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

 

プラットフォームについて: Server、Data Center、および Cloud (状況に応じる) - この記事はアトラシアンのサーバーおよびデータセンター プラットフォーム向けに記載されていますが、Atlassian Cloud のお客様も記事の内容を利用できる可能性があります。この記事で説明されている手順の実施が役立つと考えられる場合、アトラシアン サポートにお問い合わせのうえ、この記事を紹介してください。

問題

When user tried setup the DVCS Connector on our JIRA instance to communicate with the Bitbucket. User want the link be setup at a project level so that

1. Access is isolated to that project
2. Each project can link to a different bitbucket account

原因

Based on the Linking Bitbucket Cloud and GitHub accounts to JIRA Software documentation , it is stated that :

After you link an account, JIRA Software automatically starts looking for commits that reference issue keys. The summary shows the synchronisation results and errors, if any. A synchronisation of commit data from the DVCS repository to JIRA Software can take some time. As the synchronisation progresses, the commits appear in related issues. You can always enable and disable the linking of repositories with JIRA Software as needed.


This means that, all Bitbucket does is reference issues from JIRA, and nothing else.
Therefore, the links cannot be setup into project level so that JIRA will only looks for a specific project key in the commit references from a particular Bitbucket account.

It's not possible to configure JIRA-Bitbucket link to a specific project. If an issue key from a different project is accidentally entered during the commit, the comment, time, and transition of an issue will happen only if the user has permission to do so in that project. In other words, it depends on the Permission Scheme of that project. 

回避策

Create a new project in Jira with permissions , then perform bulk move all the issues to the projects manually after the issues were linked with the BitBucket accounts.

最終更新日 2018 年 11 月 2 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.