TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Support / Bug fix Issue workflow pain points

2 pointsby h0h0h0about 1 year ago
I&#x27;m interested to know how people structure support and bug fixes in the same issue management system or if that is a footgun.<p>This happens often enough where a &quot;support ticket&quot; in JIRA turns into a bug fix that has a positive affect on more than just the customers support ticket.<p>Example: A support ticket comes in on a particular problem. In Jira the ticket title is &quot;Customer Y says Screenshot button isn&#x27;t working&quot;. Dev goes in and discovers It&#x27;s not working and affects all safari browers and makes the fix, pushes to prod. Customer Y is happy now, as well as all other customers who are using Safari in future.<p>What&#x27;s the most nimble way for the org to articulate and track what was fixed software side and also articulate the support ticket is satisfied?<p>* Do you update the bug title from &quot;Customer Y says Screenshot Button isn&#x27;t working&quot; to &quot;Safari Screenshot not working&quot; * Do you go and have a new bug ticket created with a more clear title and keep the old ticket around as the &quot;support ticket&quot;? * Should we split support tickets out from the JIRA software project and keep them separate?<p>Note: While I&#x27;m using JIRA in this instance i feel like this goes for most developer issue management software that is used and I&#x27;ve never found a really elegant flow. I am open to hearing about all experiences!

1 comment

ILIWYCMBgPicChaabout 1 year ago
Keeping linked tickets seems like the best practice to me. Especially as organizations grow, a single reported issue could wind up being work tickets for multiple teams, and even make it into product management roadmaps for longer-term fixes.<p>Sometimes a bug will have a short-term fix to stop the immediate pain, but also have a long-term fix that might include re-working an entire feature.<p>Using Jira (or other similar app&#x27;s) linking features is the easiest way to keep track of these dependencies.<p>To use your example, the individual customer who reported the issue wants to know the status of the ticket &quot;Customer Y says Screenshot button isn&#x27;t working&quot;, and hopefully there is a self-service way for them to get that information. Whereas, all customers will want to know (likely as part of some relase notes) that &quot;Screenshots in Safari are now Supported.&quot;