Why my Jira App was rejected for timeout.

Raymond_sx9y0v

 

1. After submitting the app, I received an email saying that a JIRA ticket (ECOHELP-94575) had been created so I could track the review progress.

2. However, I never had access to that ticket throughout the process — the link always showed that I didn’t have permission.

3. Ten business days later, I was notified that the app was rejected due to a timeout, without any visible review updates or access to the referenced JIRA issue. 

Because I couldn’t see the ticket, I had no way to know what caused the delay, whether any action was needed from me, or whether the review was stuck. This lack of visibility makes it difficult to understand why the timeout happened or how to prevent it in future submissions.

I would like clarification on:

• What specifically caused the timeout?

• Why I was not granted access to the tracking ticket (ECOHELP-94575)?

• How to avoid the same issue during the next submission cycle.

Raymond_sx9y0v

I identified the root cause of the issue. The ECOHELP ticket generated during the app submission contained several questions from the review team that required my response, but I did not have access to that ticket. Since I couldn’t view or address those questions, the review process eventually timed out.

 

The lack of access to both the ECOHELP ticket and the Service Desk was caused by a permission issue introduced during Atlassian’s ECOHELP migration. I also wasn’t able to submit a Service Desk request to resolve it. I had to escalate through other channels and contact support from another product team to get the permission problem fixed. Now the access issue has been resolved, and I can finally view the comments within the ECOHELP ticket.