Communicate with Jira via Bitbucket

Forge
, ,
1

Hello,

I’ve been working on a Forge App in Bitbucket where I implemented a “bitbucket:mergeCheck” to verify if all issues are in the correct status using a JQL query. However, I’m having trouble communicating with Jira from the Bitbucket Forge app. I attempted several approaches with “requestJira”, but I keep encountering errors that I haven’t been able to resolve.

Here’s the code I’ve been trying to run:

const ress = await api
    .asUser()
    .requestJira(route`/2.0/repositories/${username}/${slug}/issues`);

Depending on whether I use the “asUser” or “asApp” function, I get different error messages. When using “asUser”, I receive:

PROXY_ERR: Forge platform failed to process runtime HTTP request - 401 - AUTH_TYPE_UNAVAILABLE

And when using “asApp”, I get:

PROXY_ERR: Forge platform failed to process runtime HTTP request - 400 - INVALID_REMOTE

Does anyone know the intended way for this issue or can help me out?
Thank you in advance!

2

Welcome to the Atlassian developer community @NoahEhlert,

The first problem is that’s not a valid Jira REST API route. That route is valid for Bitbucket to get its built-in notion of issues, but that’s not going to work for Jira.

But, even if it were a valid Jira route, I don’t think it will work. You might want to see this thread on the same topic:

1 Like
3

Thank you for the quick response!

The main problem I’m facing is that I want to communicate with Jira (not specifically with JQL querys) to get some information about issues.

What is the recommended way to communicate with Jira from a bitbucket-forge app?

4

@NoahEhlert,

The short answer, there’s not a recommended way. The other thread has a potential, unsupported work-around using fetch.

1 Like