アプリケーション リンクと信頼済みアプリケーションのトラブルシューティング
Portlets have been deprecated in JIRA 4.0. If you're upgrading to JIRA 4.x, consider a tandem upgrade to a Confluence version that supports gadgets, then change the jiraportlet macros to use gadgets instead. See Migrating from JIRA Issues and JIRA Portlets to Gadgets.
Please ensure that you are not running multiple Atlassian applications in a single Tomcat container. See this FAQ for more information.
JIRA Integration
Below are the warning messages which may appear on your Confluence page, above the output of the JIRA Issues macro. Make sure to check the JIRA Integration FAQ.
Warning Message | 原因 | ソリューション | Warning Message Can be Turned Off? |
---|---|---|---|
| JIRA is running over SSL | いいえ | |
| The logged-in Confluence user is not registered in the JIRA user base. | Add the username to your JIRA user base. It is highly recommended that your JIRA and Confluence instances share a common user base. | いいえ |
| Your JIRA instance has not been configured to trust your Confluence instance. | One of the following solutions:
| |
| Your JIRA instance is not able to handle trusted communications (i.e. the JIRA version is earlier than 3.12.0). | One of the following solutions:
| |
| There is a date/time difference between the JIRA server and Confluence server. | - |
アプリケーションリンク
Primarily, JIRA is set up to trust Confluence, unless you are using the Applinks plugin.
データベース
The entries are stored on the trustedapp
table in JIRA and the KEYSTORE
table in Confluence. These entries should match, if there is a trust in place. One common troubleshooting approach is to truncate these tables and begin again.
Confluence ナレッジベース
Jira のナレッジベース
Open Bugs and Features in the Confluence Project in JIRA Bug Tracker
Open Bugs and Features in the JIRA Project in JIRA Bug Tracker