コミット オプションを構成する
プラン設定の構成
このページの内容
関連コンテンツ
- Connect Bitbucket to PostgreSQL
- Connect Bitbucket to Oracle
- Connect Bitbucket to an external database
- Connecting Bitbucket Server to MySQL
- Bitbucket Server fails to connect to SQL Server: The database name component of the object qualifier must be the name of the current database.
- Unable to Connect to SQL Server Due to Error: 18456, Severity: 14, State: 12
- Connect to named instances in SQL Server from Bitbucket Data Center
- Migrate Bitbucket Server from Windows to Linux
- Install Bitbucket Server on Linux
- Install Bitbucket Server on Linux from an archive file
This page discusses the usage of Portfolio for Jira live plans (any version from 2.0 to 2.27). If you're using the redesigned planning interface, see this page instead.
By committing issue assignees, manually assigning a team member to an issue in Portfolio for Jira will update the corresponding issue in Jira when plan changes are committed.
- Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
- Click more (
) next to the plan name > Configure > Commit of changes. - Select On to automatically commit issue assignees set in Portfolio for Jira to Jira.
Note that if you don't enable this option, whenever you change an issue assignee in Portfolio for Jira, it won't affect the Jira assignee even if you commit the changes.
最終更新日: 2019 年 12 月 23 日
関連コンテンツ
- Connect Bitbucket to PostgreSQL
- Connect Bitbucket to Oracle
- Connect Bitbucket to an external database
- Connecting Bitbucket Server to MySQL
- Bitbucket Server fails to connect to SQL Server: The database name component of the object qualifier must be the name of the current database.
- Unable to Connect to SQL Server Due to Error: 18456, Severity: 14, State: 12
- Connect to named instances in SQL Server from Bitbucket Data Center
- Migrate Bitbucket Server from Windows to Linux
- Install Bitbucket Server on Linux
- Install Bitbucket Server on Linux from an archive file
Powered by Confluence and Scroll Viewport.