Skip to main content
Open

Add a new "Bug" topic type for bug reports

Related products:CC Topic Creation
dan_wiegert
tom_gerth
devin_stevens
  • dan_wiegert
    dan_wiegert
  • tom_gerth
    tom_gerth
  • devin_stevens
    devin_stevens

Blastoise186

Evening!

This is a bit of an unusual idea that I’ve actually hinted at a few times in recent weeks (including under my alias on a certain webinar), but I’ve decided that I want to submit this idea properly.

One of my heaviest use cases with inSided overall, is making use of the Community features to submit bug reports in a way that’s a bit more open and transparent, allows the use of integrations like Jira but also doesn’t result in me creating a huge number of support tickets that can’t be resolved without escalations anyway. It’s also less pressure on the support team at my home base, since I’d otherwise be flooding them a bit too often. Forums work great for this.

However, there can be a bit of a snag. Bug reports definitely aren’t “Ideas” as such, they’re not general discussions and they’re not really suitable to be Questions, because it can clog up the unsolved questions list - especially if a power user such as myself creates a high volume of them.

It would be really nice for there to be an option of a “Bug” topic type, that can be used to help distinguish actual questions or problems where someone needs help, from threads where a user is simply letting you know they broke your product and wanted to submit their findings. This isn’t something I’d intend to replace existing tools like Jira of course, but mainly something that just makes it easier to search, filter and sort through them. And most importantly, to help avoid the unsolved questions list from being overloaded!

You could potentially do more with it in the future, but for an initial implementation, it could potentially start out as more of a cosmetic thing. :)

7 replies

daniel.boon
Forum|alt.badge.img
  • Helper ⭐️⭐️⭐️
  • 730 replies
  • April 21, 2021

Thanks for sharing this idea @Blastoise186 - let’s see if any customers would find this useful too. Given the different workflows in place for handling bugs, I’d imagine this would need to be tightly coupled with a bug management tool (like Jira) to be efficient.


daniel.boon
Forum|alt.badge.img
  • Helper ⭐️⭐️⭐️
  • 730 replies
  • April 21, 2021
Updated idea status NewOpen

adam.ballhaussen
Forum|alt.badge.img+1

@Blastoise186 I love this idea. We’re currently trying to solve for a clean and easy way to share Known Issues with our customers here at Docebo and can’t really find a great tool to do so. Zendesk doesn’t offer anything out of the box, I’m unaware of whether or not Jira offers a customer facing page, and our status page is not sophisticated enough to support everything we’d like a known issues page to support (like our customers being able to share feedback with us in real time during an outage/issue).

 

The best idea we’ve come up with thus far is to create a discussion category where only our employees can post, but anyone can comment. We’d then share a post any time there’s an issue severe enough to share with our community, and provide status updates on that specific post via comments.

 

I could see a new Bug or Issue content type supporting this use case well. It could be identified via the UI as different from a question, conversation, or idea, and could potentially involve customizable statuses related to the bug, similar to Ideas, but customizable to align with how our product team classifies bugs/issues.

 

While an integration with a bug management tool like Jira would be nice, we’re going to have to handle this manually from the start, so a non-integrated option would be a great first step.


Blastoise186
Forum|alt.badge.img
  • Author
  • Helper ⭐️⭐️⭐️
  • 538 replies
  • August 2, 2021

Yeah, definitely true there!

Technically speaking, Jira can do what you’re after directly and natively. But there are a few snags with that. Here’s a few examples:

  • You’d have to make the Jira Project(s) Public which could expose stuff you don’t want to reveal to literally the entire planet
  • Jira isn’t the most user friendly thing in the world to those who don’t use it on a regular basis
  • It’d require yet another set of credentials for everyone to remember
  • Public/Anonymous users can only usually get to Issues via the List and Issues Search views, which are usually pretty ugly looking when you compare them to say… A Kanban Board, Roadmap, Agile Board or similar.
  • You’re sending users off-platform which would feel kinda weird
  • You’d probably have a huge increase in your Atlassian Cloud bill from all the users who join your Site!!!

This is kinda why I think having some clever tricks within inSided would be ideal. For the initial releases, yeah I definitely would agree that just having Bug/Issue as a content type makes sense. More stuff can always be spawned off it in the future, but if it at least helps to separate Bugs from Questions then that’s already a great start. For example, it could later be synchronised to Jira so that if the status gets changed in Jira from say, In Progress → Fixed then that’d show up on inSided as well by going from perhaps Investigating → Resolved in the next update. Or something similar.


adam.ballhaussen
Forum|alt.badge.img+1

Love it @Blastoise186 !


adam.ballhaussen
Forum|alt.badge.img+1

Blastoise186
Forum|alt.badge.img
  • Author
  • Helper ⭐️⭐️⭐️
  • 538 replies
  • August 11, 2021

Ok, I’ve just had a play with Jira for myself (because I now have my own personal instance, muhahahahaha!) and yeah… There’s definitely not a way to make this possible in a realistically usable manner on that side without the snags I mentioned. Trust me, I’ve tried testing it with Jira Software, Jira Service Management and Jira Work Management too. The closest I could find was the Announcements feature in Jira Service Desk, but even that only lets you have a single announcement at a time - and doesn’t appear everywhere either. So it’s only really useful if you want to make a specific announcement, such as about an outage.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings