-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
When a project is created, intermittent automation errors are triggered, pointing to permission issues and fields that can't be edited based on devs discussions this is because when sending the project created webhook before the custom fields schema is ready.
Steps to Reproduce
- Create an Automation Rule as per the below setup:
- add a GET request to the project to get the field configuration.
- add a GET request to the project to get the issue-type schemes
- Then create issues (Epics) among other things
Expected Results
When a project is created all the conditions of the rule run successfully with no errors.
Actual Results
The automation rule is failing intermittently.
See the logs below.
7/11/24
3:51:29.337 PM
{ [-]
account: 815843069303
ctx: { [-]
AWSRequestId: f40cd065-1764-592a-95d9-8f6f5f6593ce
clientkey: jira:02c78ea9-223d-463a-882f-90ef9396424a
cloudid: ecda8a09-b4d3-425b-a198-06878ef2c5f2
executionid: 38c4fb27-ed2f-4045-9ef0-3818f5a5d7a7
hostproduct: jira
tenantid: e98dfaac-5123-4f85-be76-824a855b1476
traceid: 95674488-e197-41f0-ab13-dd5912f5a506::00::95674488-e197-41f0-ab13-dd5912f5a506
}
env: prod
group: /aws/lambda/automation-prod-100431-05d69c8177-queueconsumersqs
level: INFO
ll: LLINFO
logger: com.codebarrel.tenant.client.http.HttpClientImpl
message: zinnia.atlassian.net:443 POST /rest/api/2/issue HTTP/1.1.
Request headers: {}
Status: [403].
Response headers: {Transfer-Encoding=[chunked], Server=[AtlassianEdge], X-Content-Type-Options=[nosniff], Atl-Traceid=[16f9b6c73ddf4c04a08d913a26866376], Date=[Thu, 11 Jul 2024 20:51:29 GMT], Strict-Transport-Security=[max-age=63072000; includeSubDomains; preload], Cache-Control=[no-cache, no-store, no-transform], Nel=[<REDACTED>], Report-To=[{"endpoints": [{"url": "https://dz8aopenkvv6s.cloudfront.net"}], "group": "endpoint-1", "include_subdomains": true, "max_age": 600}], Timing-Allow-Origin=[*], X-Xss-Protection=[1; mode=block], X-Arequestid=[2ef8c006e644e53091745983c837e0a4], Content-Type=[application/json;charset=UTF-8], X-Aaccountid=[557058%3Af58131cb-b67d-43c7-b30d-6b58d40bd077]}.
Response body: {"errorMessages":["You do not have permission to create issues in this project."],"errors":{}}.
Took: 7268ms.
stream: 2024/07/11/[$LATEST]9daa8e83c59647c18cf3e1d95aca3774
thread: main
}7/11/24
3:51:22.068 PM
According to devs, this is indeed a race condition, and the rule is executing faster than the Jira create issue modal can finish
Workaround
suggest using the new delay step as a temporary measure before the create issue happens while this bug is addressed.
Slack Thread: https://atlassian.slack.com/archives/CSBJ73LMT/p1721263057474129?thread_ts=1721256764.124299&cid=CSBJ73LT
