avinashjn

Working on a Testing Platform for the Post AI world

https://bugasura.io

Second the mp4 part. We started with gifs on bugasura.io and ended up with a pageinsights at 20!

Apparently these gifs are loaded along with the other assets and lazy loading them is not simple.

We moved to mp4 and the scores have increased quite a bit.

We use Intercom chat which is connected to our internal Slack at Bugasura.io (we are building the modern bug tracker)

It is quite difficult to get to talk to the users unless they have technical query.

Some things that work for us

1. Having the chat helped moved people further up the funnel 2. The chat offers to help at different points in the product (you can setup rules in intercom to bring up the chatt) 3. We also talk to paid users via email proactively (not many at this time) and funnel their input to the sprint

Hope it get rids of google wrapping URLs in emails

no, it is based off a mythical man-eater called Bakasura https://en.wikipedia.org/wiki/Bakasura

We even have a catroon strip on it https://appachhi.com/blog/putting-fun-back-testing/

Will do

Email there is protonmail,Zoho mail and a few others

Gdrive - onedrive, Dropbox, etc

Gsutie - office 365, Zoho

If you want an integrated solution, then it's office 365.

Zoho is ok to start with, but there is not depth in their gsuite and email products. It feels like they have a minimal team on it

You can and India is actually safe in the tech space. But please get a local lawyer and accountant on your side first to vett documents and legalities.

There are good ones available, a quick internet search will help.

- not having a clear flow open->closed, etc. - not knowing what it means (open/closed/resolved/etc) - not knowing what the right way to close the bug via a commit is Maybe a visual representation of the flow and a text desc of what each stage means might help?

  - not having the work item and communication separated and no easy flow between the two
  - not being able to 'resolve' the issue when there is a checkup down the line

  - having to have my own shadow list of bugs I'm responsible for, i.e. when I need input from somebody else and I assign the bug to them, then it's gone from my 'assigned' tickets list.

  - not heaving a way to be reminded about bugs

  - having to bug people about updating the tickets

That one is already there. You can directly paste your images in your bug report.

Resizing and alignment also possible as we use a WYSIWYG editor.

Thanks for taking the time out to write a detailed list. It really helps.

Offline, this is something a few people have been asking. It is a nightmare though with all its sync issues and conflicts :) But something we will look into.

Fast, definitely yes. We want a < 100ms for each load, everytime. Point taken about the gifs.

URL - yes. We did have that when creating a project, but we dropped it eventually. Might be a good idea to add it a the report or bug level.

Screenshot/Recorder - here is a secret - we are building something here for Android and Chrome that records your flow and you can directly report bugs from. Android app - https://play.google.com/store/apps/details?id=com.appachhi.b... Chrome ext - https://chrome.google.com/webstore/detail/bugasura/eheemiidl... Do have a look and let us know what you think.

Custom fields - this is a hard choice. We need to balance between flexibility and simplicity.

Slack - already integrated. You can get updates on your project on slack and in a few weeks respond back as well

Dream come true - we already have that. Its called Mult-Teams and you can be in different teams all on the same dashboard. The view is tailored for YOU and not the project/team.

We just discovered linear a few weeks ago. Its a great app. Loved the method and their changelog

Thanks for the suggestions. Will definetly consider the hem.

What kind of tasks do you want to do from the CLI? Are you looking at logging bugs from your catch blocks?

Another question, what else would you like to see in linear?

Fast pages - agree and working on the < 100ms threshold for all pages

Progress bar - had never thought of a loader like this. Good suggestion.

Search - right now we are directly hitting the db, maybe we can look at redis/solr as read only mirror going forward.

Integrations - can you elaborate on this? How would integrations help?

Yes, but its a brilliant starting point!

Github does seem to have a marketplace that we could get into. Maybe something we can explore.

Sync is simple to sort out.

We were thinking of two kinds of projects 1. Private - for the internal dev teams to work on 2. Public - for external folks like end users to work with internal teams

Now I see another one which is CLIENTS only - for a restricted set of external users.

This is very true. Before we started building we looked around and didn't find anything good.

Githib issues was the nearest, but it was linked to repos and it didn't make sense for us to create repos just to use bug tracking.

Our current product has only private projects, but we are going to be bringing out public projects to get feedback from end users (similar to github issues).

This is to infact help us manage our user/customer feedback and issues.

Got the 1st and 2nd one.

What kind of integrations will help and why would you need those integrations?

How does tracking time for each bug help in your work? Is this to manage SLAs or productivity?

The multi level comenting makes sense.

I really hope you meant - closed bugs

Will checkout Sentry. What do you mean by it lacks some workflow?

We are trying to be less workflow focused and more closure focused. I do see how it might not be clear on the landing page.

You are right, we have limited features. That is because we are a small team and we want to have only the minimum features required for bug tracking (and not everything JIRA has). But, what we do intend is to go deep into this space and really question how we have all been building software and managing bugs.

The nudging people to move issues is indeed a culture thing. And the intention is to bring in culture building as part of the platform. This will reinforce and make resolving issues a much needed thing in our space.

The wrong culture is a bug, and maybe bugasura will help fix it. :)

Makes sense. The PM and the tester might want the devs to be notified, but as devs that does break our focus.

Thanks for point this out, this will help us rethink 'nudges'.

We are trying hard not to go into the project management tool mode. There are already great tools like Asana, JIRA and others filling this role.

We want to be 'A bug tracker'.

But yea, maybe a place to add estimates might make sense.

Its the ultimate dog fooding experience!

You won't believe how much fun it is to log bugs of the bug tracker, into the bug tracker which has the bugs :))

Thanks for sharing this. I never read this article of Joel. Must be because I never thought I will end up building a bug tracker of all things!

Very useful pointers there.

1. Make sense, maybe add some CANNED FORMATS for steps to reproduce will make sense.

2. true, but its now a question of FIXED RESTRICTED WORKFLOWS vs FLEXIBLE WORKFLOWS (like trello)...

3. this is already there

4. yes

5. already available

6. we have added in a 'report/respond to bugs via email' feature that lets you email in the report. Couldn't get some of our team members to change their 'emailing bugs' habit

7. yes, agree

8. Absolutely true. There needs to be a PM who does remind them though, otherwise we will have stale bugs at the end of the sprint

9. A thought might be to group a set of bugs into a feature. Maybe that can be a feature of the bug tracker

11. This is our greatest blocker as of now. Every user wants a new field to track.

I did think of putting this in 'show hn', but since we are very early and still building, I thought its good to actually listen to what can be done better.

Maybe next time, we will be in a better shape and can go on 'show hn' :)

As capableweb has pointed out, all of us have been there with the 1000+ bugs overflowing from the previous sprints/releases.

While its important to fix these issues, I don't think it actually happens anywhere.

Another approach might be to 'carry over' the CRITICAL or HIGH issues only. This way, there is lesser carry over and the team won't be bogged down.

Makes sense. We already got this in.

The bigger problem as we have more folks using it will be to KEEP it that simple.

Shopify has done a great job of keeping their initial platform clean and simple and moving all the 'advanced features' to plugins/apps.

a git based bug tracker, thats a new one!

But it does make sense. Can be offline, will be redundant and fast (as its local).

Question is how many folks out there will be at home with this?

We really thought the platform nudges (compared to a PM following up) would make a difference...Why don't you want notifications?

Excellent! Fast and simplified definitely makes sense. The visual structure as well.

What does overview of code changes mean?