User Interfaces

When a user with the Resource Viewer role clicks “New Ticket” on cloudsupport.digitalocean.com , nothing happens. The “Select a team” dropdown is empty, and there’s no error, tooltip or explanation anywhere. To the user it looks like the portal is broken, not like a permission limit. The only way to find the cause is to check your role in team Settings yourself. Why it matters: read-only roles often go to the engineers who spot problems first. A silent dead end delays routine escalations (like limit increases) and sends people around their team asking what’s wrong. Suggested fixes, smallest first: Add an empty-state message in the team picker: “Your role can’t open tickets for this team. Contact a team Owner.” Disable “New Ticket” with a tooltip explaining why, instead of letting the click do nothing. Optionally, let read-only users send a “request an Owner to file this” message from the portal. Happy to help test a fix. — Mahmudur Labib

Impossible to reach you when important, not Support Number or Chat

Summary There is an inconsistency in the Droplet creation interface when selecting the Snapshot tab. Steps to Reproduce: Go to Create Droplet Select the Snapshot tab Observe that region NYC1 is pre-selected by default Notice the error message: "Cannot restore snapshot in this region" Change region to NYC2 Change back to NYC1 Observed Behavior Initially, NYC1 shows an error saying the snapshot cannot be restored in that region. After switching to another region and back (NYC2 → NYC1), the error disappears. The snapshot becomes selectable in NYC1 without issues. Expected Behavior: If NYC1 is a valid region for the snapshot, it should not show an error initially. If NYC1 is not valid, it should consistently show the error. UI state should be consistent without requiring manual region toggling. Impact: Confusing UX during infrastructure setup May lead users to choose incorrect regions or think snapshots are unavailable Slows down provisioning workflow Suggested Fix: Ensure region validation runs correctly on initial load Synchronize snapshot availability with region selection state Revalidate snapshot-region compatibility on page load Environment: Platform: DigitalOcean Web UI Feature: Droplet Creation → Snapshot tab Additional Notes: This appears to be a frontend state synchronization issue between region selection and snapshot validation.

Currently, only snapshots can be moved between teams, which creates limitations as projects grow. Over time, a simple project may expand and require collaboration across a full team. In such cases, it becomes essential to transfer resources like domains, spaces, and droplets directly into a team without complex workarounds. The current process often forces users to download large amounts of data or give up reserved IPs, which is inefficient and disruptive. Enabling seamless project migration between teams would greatly improve flexibility and scalability for evolving workflows.

I find it very complicated to found the support’s tickets area. I think you should do it easier. I just took 10 minutes to find it. I know it's not by accdicent, you don't want to get many tickets. It's not proper and it encourage me to move to your opponents.

When a Support Ticket is created, there is the option to select the 'Affected Droplet'. However, once the ticket has been created it does not show what option was selected. Unless the droplet concerned was explicitly mentioned in the body of ticket, there is no way to relate the ticket to a specific droplet. The support ticket should show (ideally in the ticket overview view), the 'Affected droplet' option that was selected when creating the ticket.

Adding Markdown support to support tickets will allow users to more clearly describe our issues (code formatting, links, etc.). Support tickets are also our own little knowledgebase that can be referenced forever. Having some basic formatting in them will make them more readable and useful.

I have noticed that the critical option has recently been removed from the support ticket process. If you take a look at status.digitalocean.com you will see that there are several service affecting issues per month. I would appreciate the ability to log a ticket as critical. I know that people abuse this for a quick response, but you could easily implement an "abuse it once and lose it" policy.