Home » MODDING HQ 1.13 » v1.13 Bug Reports » BUGZILLA report all bugs here!
| BUGZILLA report all bugs here![message #166487]
|
Mon, 03 December 2007 20:52 
|
|
 cdunigan |
 |
Messages:132
Registered:September 2007
Location: Madison, Wisconsin, USA |
|
|
We now have a publicly accessible instance of Bugzilla at http://ja2.discusrock.org/bugzilla/ . You can create your own account with any valid email address, and start entering bugs. I know that it takes some time to get used to a new procedure, so there are no plans to stop taking bugs from the Bug Report email address or directly from the forums. But Bugzilla gives you a nice standard way to make reports, upload savegames and screenshots as attachments, and most importantly, search existing bugs to check if the bug you want to report has already been reported, and what the fix or workaround might be.
We (the Development Team ... well, okay, probably mostly me  ) will be starting to enter existing bugs from the email address and the forums into Bugzilla as we can. If you have any problems using, or suggestions for improving, our Bugzilla, feel free to drop me a PM here.
[color:#CC0000]<font size="">PLEASE TAKE NOTE:</font>[/color]
A good bug report is straight to the point:
Quote:1. Bug description
2. If bug cannot be easily reproduced on a new game, post the savegame.
(customized Ja2_Options.INI as well if savegame cannot load with default Ja2_Options.INI)
3. Detailed steps to replicate the bug
4. Version Number
(for development version aka DepressiveBrot's exes, it's the JA2_####.exe number. Number shown ingame for development version are seldom up-to-date)
5. Any mods running on top of 1.13?
If it's a graphical glitch, screenshots will do.
Coders/Modders need to be able to reproduce the bug on their side before they can do something about it.
[Updated on: Sun, 02 August 2015 15:53] by Moderator Report message to a moderator
|
Sergeant
|
|
|
|
|
|
| Re: JA2 V1.13 now has Bugzilla![message #166492]
|
Mon, 03 December 2007 21:23 
|
|
| Sergeant_Kolja |
 |
Messages:42
Registered:July 2003
Location: Hannover, N-Germany |
|
|
a word to the community:
I hope not only we developers but also the community will use the BugZilla!
To clearify:
- EVERYBODY can report Bugs there.
- Improvement requests can be reported as bug with type "enhancement". (pls.see below, too)
- Also Bug votings are theoretical possible, but JAPH should tell us more about this function, 1st.
Only the "Gunz I like to see too #1001" - thing is currently not planned to be hosted there. This is because just counting guns anybody has seen somewhen is not very impressive. Discussion should take place here, first. This is also valid for most other improvement suggestions. Please continue discussing every idea, as used before. Then elect a representative who will report this idea to us.
Please, be so kind not to report any fantastic idea you got (like 3D engine, quad-Screen-Mode and so on). As already said, such ideas could be very valuable, but should be discussed with other mates here, first.
with best regards,
Sergeant_Kolja
Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
| Re: JA2 V1.13 now has Bugzilla![message #168710]
|
Wed, 26 December 2007 06:55
|
|
| Velsku |
 |
Messages:17
Registered:November 2007
Location: Finland |
|
|
It broke.
Software error:
DBD::mysql::db selectrow_hashref failed: Unknown column 'profiles.disable_mail' in 'field list' [for Statement "
SELECT profiles.userid AS id,profiles.login_name,profiles.realname,profiles.mybugslink AS showmybugslink,profiles.disabledtext,profiles.disable_mail FROM profiles
WHERE userid = ?"] at Bugzilla/Object.pm line 69
Bugzilla::Object::_init('Bugzilla::User', 27) called at Bugzilla/Object.pm line 40
Bugzilla::Object::new('Bugzilla::User', 27) called at Bugzilla/User.pm line 131
Bugzilla::User::new('Bugzilla::User', 27) called at Bugzilla/Auth/Verify.pm line 111
Bugzilla::Auth::Verify::create_or_update_user('Bugzilla::Auth::Verify::DB=ARRAY(0xa3ad3c0)', 'HASH(0xa4b68dc)') called at Bugzilla/Auth/Verify/Stack.pm line 65
Bugzilla::Auth::Verify::Stack::create_or_update_user('Bugzilla::Auth::Verify::Stack=ARRAY(0xa3a6e64)', 'HASH(0xa4b68dc)') called at Bugzilla/Auth.pm line 77
Bugzilla::Auth::login('Bugzilla::Auth=ARRAY(0x9d26f10)', 0) called at Bugzilla.pm line 232
Bugzilla::login('Bugzilla', 0) called at /sites/ja2.discusrock.org/html/bugzilla/index.cgi line 40
Report message to a moderator
|
Private
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: JA2 V1.13 now has Bugzilla![message #173418]
|
Mon, 28 January 2008 19:12
|
|
| cdunigan |
|
Messages:132
Registered:September 2007
Location: Madison, Wisconsin, USA |
|
|
Thanks for the feedback, I'll keep it in mind. But I deliberately set it up this way for the protection of the developers. Since Bugzilla requires a valid email address as its username, freeing up browsing bugs by allowing searches without search terms (effectively displaying all bugs) allows people to browse the developers' email addresses as well. I especially don't want to allow any viewing without creating an account, since that would allow search engines to index the site and spread developers email addresses even farther. It's bad enough that they have to reveal them when they accept bugs. By the way, if anyone knows a configuration tweak for Bugzilla that would remove the display of email addresses, I'd love to hear it. From what I've seen so far, that change will require a bit of coding. Not a problem since Bugzilla is all perl, but finding time is always a challenge. Obviously, I haven't done that yet.
If, on the other hand, I hear an outcry from the community to allow browsing, and I hear from the developers that they don't mind losing their privacy, I'd be happy to change it. So far that hasn't happened.
Report message to a moderator
|
Sergeant
|
|
|
|
|
|
|
|
|
|
| Re: JA2 V1.13 now has Bugzilla![message #174962]
|
Wed, 06 February 2008 22:23
|
|
| cdunigan |
|
Messages:132
Registered:September 2007
Location: Madison, Wisconsin, USA |
|
|
Using robots.txt relies on the bot honoring it, which the less savory ones obviously won't do. I could certainly obfuscate, but that again will require a code change, and if I'm doing that much, I might as well remove them from the display entirely. I intend to work on that shortly.
Anyway, it isn't just the crawlers and random browsers that I want to keep from viewing the coders' email addresses. Not all coders are comfortable with registered users being able to see their addresses. It's not that they fear some of us overwhelming them with unwanted contact. It's simply a desire for a certain level of privacy that I think they're entitled to. I'm not trying to be difficult, I'm just trying to protect the coders who have brought, and continue to bring, this wonderful game to us for no personal gain. A little respect for their privacy seemed like the least I could do in gratitude.
So, as I said before, to achieve more usability and still protect privacy, I'll start work on removing the assigned user from the bug display. Until I complete that, please continue to use JaggZilla as it is, knowing that your inconvenience is helping protect the people who gave you such a great game.
Report message to a moderator
|
Sergeant
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: JA2 V1.13 now has Bugzilla![message #182477]
|
Tue, 22 April 2008 18:42
|
|
| cdunigan |
|
Messages:132
Registered:September 2007
Location: Madison, Wisconsin, USA |
|
|
@Kermi: I'm sorry about that, and I'd like to fix it. Could I ask you to try again and tell me what happens, and I'll look through the server logs and see what I can find out? In any event, if it fails, I'll be happy to create an account for you manually.
The last bit goes for everyone. If you can't create an account normally, drop me a PM here, or send me an email (my email address is in a few links right there on the home page), and I'll be happy to create an account for you.
Report message to a moderator
|
Sergeant
|
|
|
|
| Re: JA2 V1.13 now has Bugzilla![message #183108]
|
Mon, 28 April 2008 20:31
|
|
| cdunigan |
|
Messages:132
Registered:September 2007
Location: Madison, Wisconsin, USA |
|
|
This is a brief tutorial on the "whining" feature of Bugzilla. If you'd like to be automatically notified of new bugs that are assigned to you if you're a developer (that word includes non-coders on the team), or create other kinds of automatic notifications, you use whining. Note this currently is enabled only for the Dev Team. If everyone else wants it, and you can give me a good reason, I'll turn it on for all users. If the server starts to send too much email traffic, though, I'll have to turn it off again. The guy who's hosting JaggZilla for me doesn't mind incoming traffic at all, but he really doesn't want a lot of outgoing traffic. Besides which, you can and should get notifications of bug changes by adding yourself to the CC list for the bugs you're interested in.
On to the tutorial. On your home page, click the link at the bottom of the page next to "Saved Searches" called "My Bugs." That's the default saved search everyone gets, but you can't use it for whining, so you have to create a new one. When the "My Bugs" search result list comes up, copy this saved search by entering a new name (let's call it "New Bugs Assigned to Me" for an example) under the "Remember search" button, and click the button. Your new saved search will appear next to "My Bugs," click on it. When the "New Bugs Assigned to Me" search result list comes up, click on the "Edit Search" link. What you'll see is the list of search parameters. Under "Status," select "New" and "Reopened." Don't select just "New" in case someone actually uses Bugzilla the way they're supposed to, and reopens a previously closed bug instead of just creating a new one.  Under "Email Addresses, Bug Numbers, and Votes," make sure only "the bug assignee" is checked. Then click the "Search" button to execute this search. When the search result page comes up, just click the "Remember search" button again, the name you gave this search should already be in there. Congratulations, you've created a saved search for all newly opened bugs assigned to you.
Now go to the link at the bottom of every page called "Whining," next to "Edit." On the Whining page, click the "Add a new event" button. Put whatever you'd like in the email subject and text, then click the "Add a new schedule" button. Set how often you'd like JaggZilla to run your search and email you a list of results. If you've already created saved searches, make sure the one you just created is selected under "Search." When you've set everything on this page, click the "Update/Commit" button.
Now JaggZilla will whine at you for all new bugs assigned to you. It does this continuously, not just once at bug creation/opening. The idea is that you're supposed to look at the bugs and change the status to "Assigned." This indicates that you've accepted the bug. Don't think the fact that you already show as the assignee means that the bug status has changed. It'll still be "New," and JaggZilla will still whine at you, until you update it to "Assigned." If you don't want to accept it, reassign it to someone else.
Thanks!
Report message to a moderator
|
Sergeant
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Pages (42): [1 ] |
  |
Goto Forum:
Current Time: Sat Nov 30 12:00:29 GMT+2 2024
Total time taken to generate the page: 0.03001 seconds
|
Blog
Search
Help
Members
Register
Login
Home
