Kenpachi Posted January 4, 2012 Posted January 4, 2012 Hello. I'd like to suggest creating a category called "rAthena Bug Archive" where processed rAthena bugs can be stored. ("eAthena Bug Archive" is for eA bugs...) And additionally I like to have the categories (Core, Databases, etc.) inside the archives, too. (This will make it easier to find old bugs. Current eA archive has 2028 unsorted issues in it...) Thanks for reading.
Brian Posted January 5, 2012 Posted January 5, 2012 Can we consider locking "resolved" bugs kind of like archiving? To search for un-resolved bugs (New, Confirmed, Started, or Needs More Info) just change the filter to only show Open issues.
Kenpachi Posted January 5, 2012 Author Posted January 5, 2012 I know the filter. But what's the point of having an archive if it's not used/full of trash?
Brian Posted January 5, 2012 Posted January 5, 2012 hmm, we could remove "eAthena Bug Archives" and put all the bugs back in their categories. Advantages to having an Archive section: - being able to see less bugs in the Core, Script, etc. categories Are there any other advantages?
Arcenciel Posted January 5, 2012 Posted January 5, 2012 Advantages to having an Archive section: - being able to see less bugs in the Core, Script, etc. categories I think it'll be great to see less bugs in the main sections. Just shows how much work is being done or, negatively, how much people aren't finding any bugs....
Maki Posted January 5, 2012 Posted January 5, 2012 I'd like to suggest creating a category called "rAthena Bug Archive" where processed rAthena bugs can be stored. ("eAthena Bug Archive" is for eA bugs...) /me has been advocating this since day one =p
Brian Posted January 6, 2012 Posted January 6, 2012 Fineeee =p As long as the rAthena Bug Archives has sub-categories for all (Core, Docs, Scripts, Skills). Archiving into 1 category is messy =[ I can create the archive categories this weekend if someone else doesn't get to it before then.
Brian Posted January 7, 2012 Posted January 7, 2012 I created the rAthena Bug Archives category and created all the sub-categories, but there are some issues: I just realized this version of IP Tracker doesn't have the "Prune / Mass Move" like IP Tracker for IPB 2 Another inconvenience is that "Versions" (Trunk, Stable, Renewal, Charmerge, eAPP) are separate for each project. I remember Ind and I had to edit it so when you move a bug to another project, it retains its Status (but in the database, the status_id is changed to match the new project)
Kenpachi Posted January 9, 2012 Author Posted January 9, 2012 I just realized this version of IP Tracker doesn't have the "Prune / Mass Move" like IP Tracker for IPB 2 We don't have to mass move something unless you decide to add the sub-categories to "eAthena Bug Archive", too. (If you decide to do so I'm willing to move all that topics.) Another inconvenience is that "Versions" (Trunk, Stable, Renewal, Charmerge, eAPP) are separate for each project. I remember Ind and I had to edit it so when you move a bug to another project, it retains its Status (but in the database, the status_id is changed to match the new project) It ratains the version and inside the database the ID is updated to the according ID in that project? In my opinion that's nice behaviour. (Maybe I misunderstood you?)
Recommended Posts