#88 closed task (fixed)
Replace BugWindow with new version that links to trac ticket creating
| Reported by: | Kevin Milner | Owned by: | Kevin Milner |
|---|---|---|---|
| Priority: | major | Milestone: | OpenSHA 1.1 |
| Component: | sha | Version: | |
| Keywords: | Cc: | Peter Powers |
Description
Instead of the current e-mail based BugWindow?, it'd be nice if instead the user was presented with the option of automatically submitting a ticket. Basically they would click a link which would open the newticket page in their browser with the stack trace already embedded in the description field.
Change History (7)
comment:1 Changed 14 years ago by
| Summary: | look into automatic ticket generation to replace BugWindow → Replace BugWindow with new version that links to trac ticket creating |
|---|
comment:3 Changed 14 years ago by
Ned, Peter, have you tried this? Any comments?
Note that a way to make the apps crash is:
- launch either the nightly build version or latest eclipse version of Hazard Curve Local
- select the "plot cybershake data" control panel
- click "setup rob plot" at the bottom, it should crash
comment:4 Changed 14 years ago by
Doesn't this require the user to have an account in Trac in order to submit a ticket? (I can't submit a ticket without logging in)
comment:5 Changed 14 years ago by
Looks good. I thought the captcha was failing last week but it seems fine now. Ned, sometimes logout in trac doesn't work so well and you might be in some limbo state. Try quitting your browser and then running HazardLocal?. You should get the ticket form with a captcha to prevent bot-spam.
Put 'Submit Bug Report' above email address
Add '(optional)':
Your E-mail Address (optional):
Correct spelling of 'Excpetion:'
Rearrange the data to increase the likelihood that we'll get additional feedback (e.g. 'steps to reproduce). There currently a few lines down and may not be seen.
Steps to reproduce: (PLEASE FILL IN)
Other info: (PLEASE FILL IN)
Application: HazardCurveLocal?
Version: 1.0.2
Bulid Type: nightly
Excpetion:
comment:6 Changed 14 years ago by
Thanks for the feedback Peter, I'll get on that!
I fixed the captcha issues a couple weeks ago...basically the api key was only valid for opensha.usc.edu, and not opensha.org. Let me know if it ever acts screwy again.
it looks like it's possible....see: http://www.mail-archive.com/trac-users@googlegroups.com/msg12137.html
We could then have a new dialogue which presents a link to submit a but report, then links to either quit the application or continue working (with a warning that it may be unstable).