Purpose

This page will assist you in troubleshooting the Development Panel when connecting Jira (now Jira Software) to development tools, e.g. Bitbucket, GitHub, Bamboo, Fisheye/Crucible, etc.

• Why don't I see the Development Panel?
• Why do I only seeing "Create Branch" in Development Panel?
• Couldn't read data from Stash. Learn about this issue or go to application links to fix it
• How can I limit application link of Stash, Fisheye/Crucible, GitHub, or BitBucket per project?
• Jira is having difficulty contacting Stash. If this condition persists, please contact your Jira administrators.
• Why Development Panel still not working
• Why some of the commits is not showing

• Why the "Deployed to" field is missing from the Development Panel

Solution

Why don't I see the Development Panel?

Could be of several reasons:

1. Your version of Jira is prior to Jira 6.1
2. The application links to the development tools are not configured properly
3. Development Integration Plugin might be disabled as per Development Panel missing when viewing an issue in Jira server
4. User may not have the View Development Tools permission in the permission Scheme being used
5. The issue key is not present in the title of the review

Why do I only see "Create Branch" in the Development Panel?

1. Your version of Jira is prior to Jira 6.2
2. The application that is linked to Jira Software may not support the functionality yet. The following are required:
   1. Stash 2.10 (now Bitbucket Server) and later
   2. Fisheye/Crucible 3.3 and later
   3. Bamboo 5.4 and later
3. Check that these plugins are enabled in Bitbucket Server. They expose the REST endpoints for Jira Software to be able to query data:
   

   1. Dev Status Plugin - Vendor: Atlassian - Add-on key: com.atlassian.plugins.atlassian-dev-status-plugin

   2. Stash Dev Summary Plugin - Vendor: Atlassian - Add-on key: com.atlassian.stash.stash-dev-summary-plugin

4. Check that the Remote Link Aggregation REST API endpoint is returning data for an issue key
   1. If no information is associated with that issue key, it could indicate an issue with how the repository is being indexed. If commit data is returned, it could indicate an issue with the Application Link. The following REST endpoints are available in the development tools, replace the Jira issue key with an appropriate value for your system.

 
{
  "targets": {
    "TEST-5": [
      {
        "type": {
          "id": "repository"
        },
        "count": 1,
        "objects": [
          {
            "lastUpdated": "2015-07-09T23:03:52.000+0000",
            "count": 2,
            "commits": [
              "ecf82f4d693405ded1ed5f351bd08b99d5034e00",
              "dc82ee974d8dd56ea441a76e661daec3fec0b498"
            ],
            "type": "git"
          }
        ]
      },
      {
        "type": {
          "id": "review"
        },
        "count": 1,
        "objects": [
          {
            "lastUpdated": "2015-04-27T19:37:31.642+0000",
            "state": "REVIEW"
          }
        ]
      },
      {
        "type": {
          "id": "branch"
        },
        "count": 0,
        "objects": []
      }
    ]
  }
}

curl -u <USER> http://<SERVER_NAME>:<PORT>/rest/remote-link-aggregation/latest/aggregation?globalId=TEST-15
 
{
  "targets": {
    "TEST-15": [
      {
        "type": {
          "id": "repository"
        },
        "objects": []
      },
      {
        "type": {
          "id": "branch"
        },
        "objects": []
      }
    ]
  }
}

"Couldn't read data from Stash. Learn about this issue or go to application links to fix it" is displayed in the Development Panel

2-legged authentication OAuth is not enabled for application links to Jira Software, as per Jira Application Development panel displays error - Couldn't read data. The requirement for Development Panel is that 3LO/OAuth is to have the details shown, while 2LO is to have the summary shown. See the OAuth Troubleshooting Guide for more details on configuring the correct type of OAuth authentication.

How can I limit application links of the development tools per project?

This is not currently possible. Jira Software will provide the Create Branch option on both of the applications if Bitbucket is connected. This may cause confusion (and lead to errant branch creation) so we've created an Improvement request here: JRA-37047 - Getting issue details... STATUS

"Jira is having difficulty contacting Bitbucket. If this condition persists, please contact your Jira administrators." is displayed in the Development Panel

Ensure that Trusted Application is disabled and only OAuth Authentication enabled for the Application Link between Jira Software and development tools. The Development Panel only works with OAuth Authentication with 2-Legged Authentication (2LO) enabled.

There has been some discussion on "Allow User Impersonation" whether to have it disabled or enabled to have Development Panel working perfectly, this has been cleared off as per  JRA-38716 - Getting issue details... STATUS  where either settings should work. However, users may still encounter a bug when disabling "User Impersonation" as per  JRA-38831 - Getting issue details... STATUS .

Another reason this can happen is due to the bug  Unable to locate Jira server for this macro. It may be due to Application Link configuration. , which means that sometimes 2-Legged OAuth can remain enabled, but 3-Legged OAuth is disabled, which is not a valid configuration. This case can be resolved by removing and recreating the application link.

Server time is different between the two, as per Jira shows "Jira is having difficulty contacting <Application>. If this condition persists, please contact your Jira Administrators" message in the Development Panel

Unsupported collation is also one of the causes of this error. From the logs you might see this error :

    ****************************************************************************************************
    You are using an unsupported postgres72 collation: en_US.UTF-8. This may cause some functionality to not work.
    Please use POSIX.UTF-8 or C.UTF-8 or C or POSIX as the collation instead.
    ****************************************************************************************************

Please ensure that the collation is fixed as per :

1. Unsupported collation error thrown in Jira server using PostgreSQL
2. How to fix the collation of Microsoft SQL Server database for Jira manually
3. How to Fix the Collation and Character Set of a MySQL Database manually

Why is the Development Panel not working

There are several reasons that could contribute to this -- usually due to a misconfiguration of the Application Link or Proxy/SSL.

Please follow the Application Links Troubleshooting Guide to diagnose problems with the Application Link configuration.

Why some of the commits is not showing

This issue is only affecting Jira with Fisheye Integration where the cause is due to the Commit Message Format where there is a special characters before the Issue Key is mentioned. For example:

Message - SSD-2 Testing commit

The problem here is the "-" or "Dash" before the issue key "SSD-2". This behavior itself has been reported as a bug below:

• JSWSERVER-14893 - Getting issue details... STATUS

Why the "Deployed to" field is missing from the Development Panel

For the Development Panel to show the "Deployed to" results, one of the following conditions must be met:

• The builds commit starts with the issue key
• The issue key is manually linked after the build is created, and before the build is deployed.