Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecation of JQL search and Evaluate expression endpoints #354

Closed
nessgor opened this issue Feb 5, 2025 · 1 comment · Fixed by #355 · May be fixed by #346
Closed

Deprecation of JQL search and Evaluate expression endpoints #354

nessgor opened this issue Feb 5, 2025 · 1 comment · Fixed by #355 · May be fixed by #346
Assignees
Labels
enhancement Denotes a suggestion or request aimed at improving or adding new features to the project.
Milestone

Comments

@nessgor
Copy link

nessgor commented Feb 5, 2025

The following endpoints will be deprecated.

GET /rest/api/2|3/search - Search for issues using JQL (GET)

Impact:
Version 2 searchForIssuesUsingJql
Version 3 searchForIssuesUsingJql

POST /rest/api/2|3/search - Search for issues using JQL (POST)

Impact:
Version 2 searchForIssuesUsingJqlPost
Version 3 searchForIssuesUsingJqlPost

POST /rest/api/2|3/search/id - Search issue IDs using JQL

Not implemented

POST /rest/api/2|3/expression/eval - Evaluate Jira expression

Impact:
Version 2 evaluateJiraExpression
Version 3 evaluateJiraExpression

There is a deprecation period of 6 months, and these endpoints will be removed after May 1, 2025.

For more information, see the changelog https://developer.atlassian.com/changelog/#CHANGE-2046

@MrRefactoring MrRefactoring added this to the v4.1.0 milestone Feb 7, 2025
@MrRefactoring MrRefactoring added the enhancement Denotes a suggestion or request aimed at improving or adding new features to the project. label Feb 7, 2025
nessgor added a commit to nessgor/jira.js that referenced this issue Feb 8, 2025
…ion-of-JQL-search-and-Evaluate-expression-endpoints
MrRefactoring added a commit to nessgor/jira.js that referenced this issue Feb 8, 2025
…ion-of-JQL-search-and-Evaluate-expression-endpoints
MrRefactoring added a commit that referenced this issue Feb 8, 2025
…nts (#355)

* chore: Vulnerability fix

`npm fix audit`

* chore: fix error when running vitest

RangeError: options.minThreads and options.maxThreads must not conflict

Fixed by adding `--minWorkers=8` to `test:unit` in package.json

* test: define unit test for v3 enhanced search

* feat: implement v3 enhanced search

* chore: fix broken anchor

* test: define unit test for v2 enhanced search

* feat: implement v2 enhanced search

* chore: fix typo in v2

* chore: fix wrong interface name

* test: define unit test for v3 jiraExpressions

Only implemented unit test for the newly added function evaluateJiraExpressionUsingEnhancedSearch()

* feat: implement v3 jiraExpressions

Implemented new function evaluateJiraExpressionUsingEnhancedSearch()

* test: define unit test for v2 jiraExpressions

Only implemented unit test for the newly added function evaluateJiraExpressionUsingEnhancedSearch()

* feat: implement v2 jiraExpressions

Implemented new function evaluateJiraExpressionUsingEnhancedSearch()

* chore: change minWorkers to 1 for vitest

---------

Co-authored-by: Vladislav Tupikin <MrRefactoring@yandex.ru>
@MrRefactoring
Copy link
Owner

Will be released in v4.1.0

@MrRefactoring MrRefactoring linked a pull request Feb 20, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Denotes a suggestion or request aimed at improving or adding new features to the project.
Projects
None yet
2 participants