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

Issue tracking: PS! edition #2297

Closed
panpawn opened this issue Nov 26, 2015 · 11 comments
Closed

Issue tracking: PS! edition #2297

panpawn opened this issue Nov 26, 2015 · 11 comments

Comments

@panpawn
Copy link
Contributor

panpawn commented Nov 26, 2015

I am working with Nineage to start thinking about creating an issue tracking system for PS! that would allow the average user to easily and effectively report bugs pertaining to relevant parts of PS!. Here's the basics of what I was thinking along the lines of for the architecture:
>user does /reportbug
The client sends the user a popup with a form asking for information pertaining to the bug, such as...

  • Title
  • Description
  • Category
  • Evidence

After the user fills that information out, it will send this to the server, where the database of issues are stored. (TSV database like the existing local ladder system...?)

>user does /viewbugs

  • A popup is displayed with all of the submitted bug reports. The user has a drop down to sort by category.
  • The user also has the option here to 'star' important and valid bug reports.
  • Bug reports that have the most stars are sorted at the top of the list

And of course, there will be a certain rank that is able to delete reports based on the report number with /deletereport [report number]

This is just a rough sketch on my idea of a issue tracking system, what does everyone else think?

@Zarel
Copy link
Member

Zarel commented Nov 26, 2015

Do we currently support popup forms? I'd guess no. Imagine a popup form asking for someone's password... such phishing...

@Zarel
Copy link
Member

Zarel commented Nov 26, 2015

Command-based just isn't a very good system...

@Slayer95
Copy link
Contributor

Mandatory xkcd: https://imgs.xkcd.com/comics/standards.png

The proposal doesn't feel like the universal standard

@Zarel
Copy link
Member

Zarel commented Nov 26, 2015

tbh, we do need some sort of issue tracker... the biggest issue with existing ones is probably that most of them cost money, and I don't trust the ones that don't not to have glaring vulnerabilities.

@panpawn
Copy link
Contributor Author

panpawn commented Nov 26, 2015

Is it possible that this kind of form could only work client-sided? That way, other servers cannot try to do another kind of popup form server-side?

@Zarel
Copy link
Member

Zarel commented Nov 26, 2015

We could, but at that point we might want to write it entirely separate from PS or something.

One idea would be to host it outside of the main server, so vulnerabilities are less of an issue. My only issue with that is that moderation/trolls could be an issue if it's disconnected from the PS login system.

@panpawn
Copy link
Contributor Author

panpawn commented Nov 26, 2015

This is semi off topic, but did PS's old forums use PS login credentials? I'm wondering if those could be optimized for bug reports...

Did those have a 'liking' or 'staring' feature by chance? (I don't remember)

@panpawn
Copy link
Contributor Author

panpawn commented Nov 26, 2015

(I want to reemphasize how useful sorting reports by categories could also be very helpful)

@Zarel
Copy link
Member

Zarel commented Nov 26, 2015

Yes, PS's old forums did. PS's old forums were also hacked. That's kind of why I said I don't really trust most third-party software these days.

@kotarou3
Copy link
Contributor

bugzilla works fine for mozilla. No idea how well it works from a end-user perspective though.

@Zarel
Copy link
Member

Zarel commented Jan 12, 2016

Now that we have #2367, we can just put approved mechanics bugs there. I'm fine with the current system for everything else.

@Zarel Zarel closed this as completed Jan 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants