Is there a reason why the link for creating DEVHELP tickets was commented out?
Hi @sven.schatter - DEVHELP is currently being refactored. We’ve been getting inundated with general support questions that belong on the Developer Community despite our best effort of describing what DEVHELP should be used for. General questions need to be posted here, on the forums.
For the special uses of that service desk (i.e. 3LO app distribution applications, email API access applications), hard links are provided in announcements and documentation.
The primary remaining use case for DEVHELP was for reporting critical bugs and issues, which is still available [here]… and likewise, app security incidents can be reported here. Likewise, app security incidents can be reported here.
The main portal is still available at http://go.atlassian.com/devhelp for the main JSD portal. Again, the removal of the link in the forum headers was due to the fact that we’re continuing to get general development questions that should be posted publicly here instead.
Thanks for the explanation and insights @nmansilla. I reported a bug almost a month ago as a DEVHELP request, and to be honest, missed that it says in the Service Desk portal that we should only use this for critical bugs.
However, I have some concerns that posting to the dev community is a better solution. Is there a chance that the bug reporting practice can be reconsidered?
Here are my concerns:
- If we post bugs to the dev community, it’s easy for them to get lost in the noise.
- There is no SLA that would create pressure for Atlassian to respond or attend our bug reports within a certain timeframe.
- There is no queue that would make sure that bug reports are picked up at some point and in fair order (similar to 1.)
- How can we escalate a bug if we don’t get any response? Tagging Atlassians is one way that comes to mind, but I feel this is a recipe for more noise (When is it appropriate to tag? How long should I wait until I tag someone?).
We often discover non-critical bugs because they are reported to us by customers, and we forward them on their behalf (in many cases, they affect our apps). By posting bugs to the community, we have no way of giving the customers any idea of when the issue will be attended or resolved.
I think I speak for many in the vendor community when I say that in recent months, it feels Atlassian is all about going full steam ahead but doesn’t seem to have resources to fix the small things that get broken along the way.
I can see a couple of benefits of having the community being the first stop for sharing bugs:
- It lets other vendors/developers see and can speak up that they’re having similar issues and propose work arounds.
- It frees DevRels folks up to help to advocate for us in other areas.
That said - agree with that for some bugs there is a need for us vendors to be able to report things because of the customer facing angle.
@nmansilla, thank you for the explanation. I raised a Request access to the Email API ticket in DEVHELP a week ago. There’s been no follow-up from Atlassian yet. I think my ticket might have been lost due to refactoring DEVHELP. Could you suggest who to contact to check that?
@kkolina Those tickets are handled by a different set of folks. I’ll ping them to check on status.
@nmansilla, thank you!
I have raised a DEVHELP issue almost a week ago, as Critical, using the Developer Support portal.
I believe that this is a bug introduced in Confluence 7.12.0, but I have had no correspondence, nor confirmation from Atlassian.
So this is the year 2021, are they still mucking us developers around?
Here is the ticket, for anyone that has access: https://ecosystem.atlassian.net/servicedesk/customer/portal/14/DEVHELP-6674
How do we get support for their bugs?