[JRACLOUD-75602] Improvements in API for search issue functionality in Jira - Create and track feature requests for Atlassian products.

Type: Suggestion
Resolution: Won't Fix
Component/s: Issue - Search - Backend - JVIS, Issue - Search - Frontend only
Labels:
- timeout-suggestion-bulk-close

Support reference count:
1
Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

Current behavior -

Install tempo and search for an issue in it to log time, it shows a different list in Jira vs Tempo as soon as we type project key

Expected behavior -

Consistency in the search results in Jira vs Tempo

We took feedback from the Tempo team and the feedback we got was -

Jira doesn’t provide the same API for the public as the one used for the default issue search

Assignee:: Annaliese Rozvany (Inactive)

Reporter:: Madhuri Godhwani (Inactive)

Votes:: 1 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 20/Nov/2020 1:29 PM

Updated:: 10/Jan/2025 2:27 AM

Resolved:: 16/Apr/2023 8:31 AM