The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible that rest/api/3/search API fails due to Email domain unverified issue

AutomationUIUser
November 1, 2023
Hi
 
We've noticed that on October 26, 2023, the rest/api/3/search endpoint either failed with a 400 error or didn't return all the issues that satisfied the JQL query. Is it possible that this issue is related to the unverified email domain problem?
 
Regrettably, we don't have any logs from when this occurred. However, the API is currently functioning correctly for issues that were not retrieved earlier using the same JQL query. Incident details suggest that it could impact content viewing. Thus, we suspect that this might be linked to the aforementioned issue.
 
Please inform us if you need any additional information.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Marko Blagus
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
November 2, 2023

Hello,

 

What do you mean it didn't return all the issues that satisfied the JQL query?

 

Best regards,

Marko Blagus

AutomationUIUser
November 2, 2023
Hi,
We have observed below case:
At time T1, we executed the JQL query:
 
{
  "jql": "id in (396718,374927,374506,374376,373228,396502,392611,388502,384843,384796,384721,392270,396129,396217,396205,396121,392938,392937,392936,391282,391292,391290,391278,391275,391274,391308,391310,391309,391305,391303,391299,391294,391295,391331,391300,391349,391347,391348,391340,391339,391335,391337,391336,391332,391329,391328,391319,391326,391317,391334,391287,391286,391285,391283,391281,391280,391276,391273,391272,391301,391345,391325,391323,391322,391320,391318,391312,391311,391306,391293,391304,391302,391298,391296,391291,391288,391321,391346,391344,391342,391343,391341,391338,391330,391327,391324,391188,391217,391229,391238,391220,391232,391218,391219,391239,391230,391231,391221,391222,391234,391235,391226,391225,391228,391233,391237,391236,391227,391223,394228)",
  "startAt": 0,
  "maxResults": 100
}
 
This query initially returned 90 records. However, at time T2, which occurred around October 26, 2023, the query returned only 60 records. Subsequently, at time T3, the query once again returned 90 records.
In the jira admin change log there was no logging for the permission change during this time and the jira issues were not deleted at the T2 time as well
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events