[BUG] JIRA Search (Independent Publisher) connector - "Search for issues using JQL" action returns "410 Gone"

Open
#4,026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
api

Research direction

Start by locating the JIRA Search (Independent Publisher) connector definition for the “Search for issues using JQL” action and compare its request with Atlassian’s /rest/api/3/search/jql migration guidance. Reproduce the 410 response with valid parameters; done means the action returns issues matching the supplied JQL query.

Written by the indexing model from the issue text.

Description

bug
Type of Connector

Certified Connector

Name of Connector

JIRA Search (Independent Publisher)

Describe the bug

When trying to use “Search for issues using JQL” action in the JIRA Search connector, the following error appears:

410 Gone – The requested API has been removed. Please migrate to the /rest/api/3/search/jql API. A full migration guideline is available at https://developer.atlassian.com/changelog/#CHANGE-2046

It appears this connector/action needs to be updated to the latest version of the JIRA API to maintain functionality.

Is this a security bug?

Yes, this is a security bug

What is the severity of this bug?

Severity 1 - Connector is broken or there's a very serious issue

To Reproduce
  1. Invoke the “Search for issues using JQL” action, providing valid parameters.
  2. Run flow
Expected behavior

The action when run should return a list of issues which meet the JQL query.

Environment summary

N/A - cloud connector

Additional context

N/A

Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/PowerPlatformConnectors

All issues in microsoft/PowerPlatformConnectors

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.