2026-07-19

✨ Faster support and delivery workflows

This release turns a batch of customer feedback into practical improvements across Service Desk, GitHub-connected work, sign-in, and everyday navigation.

📎 Email attachments now stay with Service Desk tickets

Files sent with a new support email or a later customer reply are now saved directly on the ticket. An attachment indicator and linked filenames appear alongside the exact message that included them: beneath the Customer description for the first email and beneath the matching Discussion comment for later replies. The same files remain together in the Email Attachments group on the ticket's Assets tab, so you can open them from either place.

Inbound messages can carry up to 10 attachments of 10 MB each. Unsafe active-content types are skipped, and a problem saving one attachment never prevents the support request itself from being created.

📚 Learn more: Email Channels & Setup

🚨 New email tickets get a smarter starting priority

DevStride now interprets the subject and content of a new Service Desk email and selects the closest priority configured for that ticket type. A clear outage or urgent request can arrive already elevated instead of waiting unnoticed at the default priority.

The classification never overwrites a priority supplied by a form or set by a person. If the AI service is temporarily unavailable, a conservative keyword fallback still recognizes strong urgency signals and only chooses from priorities your organization actually has.

📚 Learn more: Working a Ticket

🔗 Create an item and relate it in one step

The item drawer now includes Create Linked Item. Use it to open the normal create dialog with the current item's team, board, and parent location already suggested and a Related to connection back to the current item pre-filled.

That makes flows such as filing an issue against a story much faster: create, adjust anything you need, and save — no second trip through the Relationships dialog.

📚 Learn more: Item Workspace Quick Links

🐙 See the repository behind GitHub work

The GitHub tab now shows the owner/repository on pull-request rows, pull-request details, and branch rows. When one DevStride item collects work from several repositories, you can immediately tell which codebase each entry belongs to.

GitHub linking is more dependable too: item numbers must now appear as distinct references, so ordinary words and longer identifiers no longer create accidental links. If GitHub or Azure DevOps is unavailable or misconfigured, DevStride contains the failure and shows a useful message instead of hanging or leaking an unrelated integration error.

📚 Learn more: GitHub Integration

🔐 Clearer sign-in and invitation handling

Sign-in failures now explain what actually happened. An unknown email shows No account found for that email address, incorrect credentials keep their own guidance, unverified accounts still reach verification, and rate limits no longer masquerade as connection failures.

Invitations are also bound to the email address they were sent to, preventing an invited placeholder from being claimed through a different identity. Across the rest of the app, several API failures now surface their intended specific message — including permission, storage-limit, verification, item-loading, and import errors — instead of falling back to a generic toast.

🧭 Smoother responsive layouts and navigation

• Filter-bar controls now stay aligned to the right on Map, Analyze, Notifications, and Automations.
• Board header actions remain on one row and pinned inside the app at medium widths, while long breadcrumbs scroll within their available space.
• Item-drawer header buttons and the close strip now share consistent widths, and desktop no longer shows the compact mobile parent breadcrumb above the full path.
• Map Portfolio stops paging once a selected item cannot be found, preventing repeated network requests while keeping valid active items visible.

🧹 A quieter application

The retired Sentry and Gleap integrations have been removed. Enterprise contact requests still open the DevStride contact dialog and provide a direct email link to the sales team. Production builds no longer publish source maps that existed solely for the removed error-reporting integration.

We also tightened background observability behavior so disabled Lambda warmers stay disabled and a stale or unavailable Portfolio selection cannot generate runaway traffic.