Author Topic: Exporting Bug/Suggestion Tracker  (Read 1398 times)

Exporting Bug/Suggestion Tracker
« on: 02 Oct 2016, 12:00 »
G'day,

I think most people are keen on migrating to YouTrack another bug tracker? Especially since it seems the forum based bugtracker project hasn't been maintained in years. One step towards that would probably be to disable/remove the old forum based bug tracker.  I see this involving a few steps:

1) Make current forum bug tracker readonly with a link to YouTrack another bug tracker
2) Export tickets from forum bug tracker. Is there an export facility?
3) Import tickets into YouTrack another bug tracker.
4) Completely disable forum bug tracker.

If there isn't an export, does anyone mind if I do a bit of web scraping? I could add delays so it doesn't overwhelm the server.

Since most of it would be automated, it wouldn't be too much work to transfer over old closed tickets, does anyone care about that?  Otherwise I could just transfer over current open tickets.

Who can I hassle about this? :)

Nick.

« Last Edit: 02 Oct 2016, 23:49 by sonneveld »

Re: Exporting Bug/Suggestion Tracker
« Reply #1 on: 02 Oct 2016, 13:03 »
+1 for making the old bug tracker readonly. We have too many bug trackers.
Try harassing AGA

- Alan

Gurok

  • Rottwheelers
  • When life hands you lemons, combine them with the mop
    • I can help with AGS tutoring
    •  
    • Best Innovation Award Winner 2016, for improving and extending the AGS scripting language
    •  
    • I can help with proof reading
    •  
    • I can help with scripting
    •  
  • Gurok worked on a game that was nominated for an AGS Award!Gurok worked on a game that won an AGS Award!
Re: Exporting Bug/Suggestion Tracker
« Reply #2 on: 02 Oct 2016, 14:15 »
I'm not so keen on migrating to YouTrack. Thought it was about time I said something.

I don't find YouTrack natural to use at all. I have certainly tried; I've made a few comments there. The UI is cluttered and the tooltip labels for columns in the list view don't help. Call me stupid, but I don't understand the difference between priority and importance, or why we need both. (Isn't important stuff naturally a priority?)

It's also off on another site, away from AGS and away from the project code. I don't know what the long term goal is, but this is a confusing workflow:

Someone makes a pull request on Github
That pull request references a YouTrack issue
I want to comment on it
Do I make the comment on Github or on YouTrack?
This is more developer oriented, but: If someone digs up an old YouTrack issue, how do they go about finding pull requests that were made for it?

I mean, I think it would be a whole lot simpler to just do everything on Github. It's also the first place I think to look for bugs. Maybe this is just me :/

Sorry to be negative, but this is how I feel.

selmiak

  • ǝsıɔɹǝxǝ ʞɔǝu puɐ uıɐɹq
    • I can help with play testing
    •  
    • I can help with proof reading
    •  
    • I can help with translating
    •  
    • I can help with web design
    •  
  • selmiak worked on a game that was nominated for an AGS Award!
Re: Exporting Bug/Suggestion Tracker
« Reply #3 on: 02 Oct 2016, 19:05 »
From a user POV using github is better than having to sign up for yet another service to just write a small feature suggestion. I'd just post on the forums then and annoy everyone until someone copies it over :P

Quote from: ClickClickClick
If you kill everyone there's nobody left to punish you.

Crimson Wizard

  • AGS Project Tracker Admins
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    •  
    • Lifetime Achievement Award Winner
    •  
Re: Exporting Bug/Suggestion Tracker
« Reply #4 on: 03 Oct 2016, 00:40 »
The UI is cluttered and the tooltip labels for columns in the list view don't help. Call me stupid, but I don't understand the difference between priority and importance, or why we need both. (Isn't important stuff naturally a priority?)
These are custom fields, created by me, they are not integral part of Youtrack itself. Back then I was carried away with some ideas that are probbably more suitable for a large scale - large team project.
So they may be removed.
(The original idea was that public Importance field is to be set by Reporter (user), and private Priority field is to be set by developers. The difference between them is that something could be important for users, but too difficult to do in nearest time. Hence, the two fields.)



I however must confess, although that may sound strange coming from the person who actually spent time configuring that tracker, that I am in big doubts about Youtrack tracker too.
Not because it is bad on its own (I find it pretty versatile), but because of that GitHub/Youtrack conflict Gurok also mentioned.

Looking back, the idea about changing the issue tracker was based on two considerations:
* I did not like AGS bug tracker very much;
* I feared that github tracker will be confusing for regular AGS users, because it has a lot of coder-related stuff around (buttons, graphs, links, etc).


From a user POV using github is better than having to sign up for yet another service
You can login in Youtrack using github account.
« Last Edit: 03 Oct 2016, 00:47 by Crimson Wizard »

selmiak

  • ǝsıɔɹǝxǝ ʞɔǝu puɐ uıɐɹq
    • I can help with play testing
    •  
    • I can help with proof reading
    •  
    • I can help with translating
    •  
    • I can help with web design
    •  
  • selmiak worked on a game that was nominated for an AGS Award!
Re: Exporting Bug/Suggestion Tracker
« Reply #5 on: 04 Oct 2016, 02:39 »
From a user POV using github is better than having to sign up for yet another service
You can login in Youtrack using github account.

is youtrack some subservice of github? that's fine on my end then when I can use that same login, still from what gurok mentions this seems to fragment all this stuff even more. Why can't I login with my ags account. why can't youtrack grab stuff from the ags bugtracker. is there some yougrabmybug service maybe?

Quote from: ClickClickClick
If you kill everyone there's nobody left to punish you.

Re: Exporting Bug/Suggestion Tracker
« Reply #6 on: 04 Oct 2016, 03:33 »
Why can't I login with my ags account.  why can't youtrack grab stuff from the ags bugtracker.
Well this is the plan. Export the AGS bug tracker, convert into a format youtrack another issue tracker understands, and drop the old bug tracker. I would rather this be a one-time thing instead of trying to get multiple issue trackers in sync.

I don't think the ags accounts are exposed in a way I could integrate with youtrack another issue tracker (or github).

Nick.

Crimson Wizard

  • AGS Project Tracker Admins
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    •  
    • Lifetime Achievement Award Winner
    •  
Re: Exporting Bug/Suggestion Tracker
« Reply #7 on: 04 Oct 2016, 13:37 »
I believe the two biggest issues that have to be solved (and they are already mentioned by people above):

1. For developers: integrating with github and devising guidelines (what to do if github and youtrack issues/pull requests relate to each other).

Speaking of this, current AGS tracker had same issue for all the previous years. Regular users, especially Windows users who had nothing to do with building engine from the code, rarely went to github (maybe not everyone knows about it), it was much easier for them to put their bug reports on forums.

By giving a quick thought about Gurok's question:
Someone makes a pull request on Github
That pull request references a YouTrack issue
I want to comment on it
Do I make the comment on Github or on YouTrack?

I'd say if you are to comment implementation, then you should comment on the pull request page, of course.
The YouTrack issues are more to discuss the general (conceptual) solution: whether we do this, how we do this, etc.

This is more developer oriented, but: If someone digs up an old YouTrack issue, how do they go about finding pull requests that were made for it?
Unless this can be automated with some wizardy, someone (issue maintaner and/or project maintainer) must reference pull requests in comments to tracker issue.

2. For end-users: integrating with AGS website (making it easy to go to tracker from the site, making it easy to login).

« Last Edit: 04 Oct 2016, 13:43 by Crimson Wizard »

Crimson Wizard

  • AGS Project Tracker Admins
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    •  
    • Lifetime Achievement Award Winner
    •  
Re: Exporting Bug/Suggestion Tracker
« Reply #8 on: 08 Dec 2016, 09:19 »
*bump*

Some solution has to be found here. Whether that be using Youtrack, or else. Having 3 trackers at once is bad.
We need to weight the pros and cons.

Github issue tracker:
+ it is close to the project code;
+ it can be customized using labels (aka tags)
- you need to be registered at GitHub (not likely something that many regular AGS users have)
? will regular AGS users find it convenient to use?

Youtrack:
+ flexible and very customizable
+ accepts several common authorization types: github, yahoo, google id, yandex
? can it be integrated with github (I think it supports it)
- not visually close to the project code or community website (at least not without a link on homepage).

AGS boards issue tracker:
+ an integral part of AGS boards
- feels clunky to use and configure (or is it just me?)
- no integration with github possible


Additionally, we need a place to keep technical documentation in (like, explanation of how engine works, how to release new versions etc). So far I used wiki on Github.

« Last Edit: 08 Dec 2016, 09:37 by Crimson Wizard »

Peder

Re: Exporting Bug/Suggestion Tracker
« Reply #9 on: 09 Dec 2016, 20:27 »
Why spread things across multiple services, when everything can be kept in the same place?

My vote goes to using Github for anything it can be used for (docs, issues etc)

When it comes to dev related stuff like releasing new versions and other "major" things like that, wouldn't it be best to put those in a README file or something in the project?
The wiki would then be great for more detailed descriptions of how the engine works etc.
Subscribe to MAGSAN: http://eepurl.com/ca5dTv

Crimson Wizard

  • AGS Project Tracker Admins
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    •  
    • Lifetime Achievement Award Winner
    •  
Re: Exporting Bug/Suggestion Tracker
« Reply #10 on: 13 Dec 2016, 11:01 »
Alright, maybe there is a good point about github. In fact I was ready to move there before trying Youtrack. My only doubt was whether it will be convenient for regular AGS users.
However, thinking about it, most of the common users do not use even the built-in bug tracker. There are literally like 2 or 3 AGSers who post there regularily (not counting code contributors). Most of people are reporting bugs in the forums.