Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge bugs #2

Open
Gankra opened this issue Oct 3, 2012 · 6 comments
Open

Merge bugs #2

Gankra opened this issue Oct 3, 2012 · 6 comments

Comments

@Gankra
Copy link
Member

Gankra commented Oct 3, 2012

It would be a handy feature to be able to merge duplicates into one issue.

As a stretch: being able to provide a list of "common" or "recently reported" bugs in the actual Sburb debugger for them to be able to just select as "I also got this".

@Gankra
Copy link
Member Author

Gankra commented Oct 3, 2012

Just noticed you've sort of added this functionality as being able to label them as part of a family of bugs, but this would be more explicit in that it would put them under one link. Possibly when they're merged it could have a collapsed listing of all the reports which can be individually expanded for further examination?

@FugiTech
Copy link
Member

FugiTech commented Oct 3, 2012

I think labels solve most of what you're looking for here, they just don't have a proper interface yet. Labels can have a name, a description, and an arbitrary number of reports attached to it. Is there something else you were hoping to see?

@Gankra
Copy link
Member Author

Gankra commented Oct 3, 2012

Reducing the clutter when browsing all reports, I guess. Also not needing to explicitly create a label. They just kind of implicitly catalyze around one report. How does one go about viewing the groups? The interface for this is pretty unintuitive right now.

Also: is there a way to get these to collect around the instance? E.G. "this is just part1 bugs, this is just part2 bugs, etc..."

@FugiTech
Copy link
Member

FugiTech commented Oct 3, 2012

http://sburb.info/report/stats is probably your best jumping off point. That allows filtering by issue, url (so that you can break up which page caused it), browser, os, etc.

http://sburb.info/report/random is a quick way to sort thing into issues.

Yes, it is a terrible interface. I've been too busy to fix it :(

@Gankra
Copy link
Member Author

Gankra commented Oct 3, 2012

It's better than the absence of one than I wrote.

@Gankra
Copy link
Member Author

Gankra commented Oct 3, 2012

Also: URL grouping seems to be lackluster due to various https/www/?save additions. Grouping by the name property in the sburb node would perhaps be more effective. Version number could be used to refine it, with URL as a last resort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants