Surprisingly an app I submitted 5 days after those two, was just approved 2 days ago. So is there actually a chronological queue or not? Dun dun duuuun.
Anyway much empathy for the support team still swamped by these tickets. Something as tiny as a “your place in queue” number would surely massively reduce inbound and uncertainty.
I hope you are doing great. @ayarazarvi we have submitted a request 1 week ago to do some changes for the version we wanted to submit to marketplace (version number and compatibility change), and in order to not get delayed because of the process (I understand that there are multiple requests), we have submitted today the current version for review, but I will appreciate if we can apply these changes from this ticket first: https://ecosystem.atlassian.net/servicedesk/customer/portal/9/AMKTHELP-27206
The application was originally rejected because of the absence of a support portal link(we’re switching from free to paid). We applied for free cloud licenses of JSD(https://ecosystem.atlassian.net/servicedesk/customer/portal/9/AMKTHELP-29521), but we were rejected because we have to have at least one paid app, but we can not make our app paid because we need a support portal link ) It looks like an infinite loop )
Hey @AntonVersal , you can activate trials for confluence/jsd/jsw and use those links in the app submission, once the app is approved, you can create a free license ticket. Hope this helps.
Your new app review ticket is : AMKTHELP-30085 ( I have added you as a reporter )
Anyone have tips on getting past the “Automatic Rejection” phase? We have quite meticulously filled out all the pertinent sections, with good descriptions of our app, but still get “Automatic Rejection - Not enough details on listing”. Is this related to a particular field, or some overall word count across different fields, or…?