issueId not populated

[detsikas]

Hi everyone,

I have recently integrated Bitbucket with Jira and I see that when I try to do a bitbucket operation from within Jira, like Create Branch, the http request issueId field contains undefined instead of the actual issue id. 

This results in a 400 Bad request error.

When I manually add the ID to the request it progresses.

I have checked similar issues but they all seem related to how one adds the ID when manually using the REST API.

What I need to resolve is why Jira itself does not add the issueId to the http request it creates  and how can something like that be resolved.

Thank you,

Nikos 

[detsikas]

After searching quite a bit, I believe the problem is the installation on the Mac platform. I have installed everything on a CentOS (container!) and it all worked perfect just out of the box.

[Yogesh Mude]

HI @detsikas

Welcome, to the community!

The issue key should be populated while creating a branch from that specific Jira issue.

if not then something wrong with application link as you mentioned that you are getting 400 bad request error.

please check/try to configure/integrate Jira and bitbucket properly. 

[detsikas]

Hi,

thank you for the immediate response.

I have crossed checked everything and it all seems in place. I believe the error might be related to the dvcs connector plugin.

When I go to the DVCS accounts page in the Administration secrion, instead of a regular output I get an exception. 

Here are the first few lines

DVCS accounts

An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'loadOrganizations' in class com.atlassian.jira.plugins.dvcs.webwork.ConfigureDvcsOrganizations threw exception com.atlassian.cache.CacheException: com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.atlassian.jira.plugins.jira-dvcs-connector-plugin] at 

com.atlassian.jira.plugins.jira-bitbucket-connector-plugin:repositoryConfiguration//templates/dvcs/add-organization.vm[line 40, column 35] at 

This tells me that the bitbucket connector is trying to use the Dvcs connector and that one fails. 

I have seen answers like this one https://jira.atlassian.com/browse/JSWSERVER-14206

but my case is not the same because I do not get a null pointer exception.

I have also checked the relevant table in mysql and it is empty

mysql> select * from AO_E8B6CC_ORGANIZATION_MAPPING;

Empty set (0.00 sec)

Does this add some insight to the problem?

Here are couple of other pieces of information that may be important

1. I am using localhost for both jira and bitbucket and  I have moved bitbucket to another context path

2. I am using the same db for both jira and bitbucket

[Yogesh Mude]

Hi @detsikas

First thing is try to resolve this DVCS connector issue and then if you have been moved/changes the bitbucket context path then try to delete the old application links and then create it with ew one.

If you are using localhost then also it will work there is noting like ..

I am using the same db for both jira and bitbucket

What do you mean same DB?  

[detsikas]

By same DB I mean what you are using, same db for both jira and bitbucket.

The bitbucket context is not relevant at the moment.

I have deleted and recreated the application links multiple times but no luck.

I am focusing on the DVCS issue.

No matter how much I search I cannot seem to find answer. Everybody is facing the DVCS issue that is associate with the upgrade, but my case is not that.

I have also noticed that when I try to access development tools from the administration page of my project I get error 500 page.

I appreciate your help Yogesh. Are an Atlassian tech support member? If not how can I direct my question to Atlassian tech support?

Again, thanks a lot for the help

Nikos

[Yogesh Mude]

Hi @detsikas

Actually you should not use the same database for both Jira and Bitbucket.

If you want to contact/raise a support ticket to Atlassian, please visit to below site.

support.atlassian.com

[detsikas]

According to the documentation it is OK to have the same db for both Jira and Bitbucket. It prompts during setup too.

The support link brings me back here. Perhaps the starter license does not allow to raise a ticket?

[Yogesh Mude]

Yes, it allows. 

Please login to that portal and raise a ticket.