-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
JCMA - 1.7.5
-
Minor
-
2
Issue Summary
When attempting to update some Jira filters in cloud upon being triggered by a listener-triggered app migration event (see https://developer.atlassian.com/platform/app-migration/events/) we notice that when trying to update a filter that references a migrated project, we get a HTTP 400 response from the Jira Cloud REST API.
After a short time the filter then attempted to update will work successfully in cloud.
For example, when trying to update the filter syntax for
numberOfComments > 0 AND project = 10015
A HTTP 400 is received. This is probably not related to MIG-1224: App migration listener-triggered is sometimes sent before onStartAppMigration() is called title
After waiting a few seconds, re-try and the filter can be updated.
Steps to Reproduce
- Create some filters in Jira
- Perform a server to cloud migration in Jira
- Update the filters in Cloud
Expected Results
The filter can be updated right away.
Actual Results
A HTTP 400 is returned.
Workaround
Delay the update for several seconds.
Is anyone at Atlassian able to confirm what "several seconds" means? Are we talking about 5 or 10 seconds or more like 60, 120 or even 300 seconds?