Hi Connor,We've managed to get a list of issues that we might have with the gitlab issues tracker:1. Duplicates, Inkscape has a large number of duplicate bug reports, which are marked as such. When issues are fixed, the bug team checks the list of duplicate issues to make sure each of the issues is really fixed. GitLab currently only closes issues and doesn't really back-link or allow searching duplicates for any specific issue. Labels for duplicates must be added manually. Currently duplicate lists are our strongest indication that a problem effects many users. Having a search would probably allow us to make sure cascaded duplicate issues were tracked, rather than a flat list of direct linking which would not.2. Comment edits aren't recorded, so bug trackers don't know if details have been changed. We don't know if there are notifications for edits, so we can't know if a bug requires attention. Could editing comments be turned off project wide?3. This one's harder, but launchpad has the ability to link bugs to multiple projects. A bug might be shared between two projects or it might be moved from one to another. A good example is when website issues are reported in lp:inkscape but then can be moved to lp:inkscape-web. This is due to how bugs in launchpad have 'bug_tasks' which link issues to projects.4. Bug dependence, currently we can't see a way to set one issue as requiring another issue to be completed. But this might just be task lists and we're not used to how this works.5. We get a lot of wishlist items, so we'd probably want to filter these out. Not sure if issues can be approved before being committed, or if closing many many bug reports is the way to go. If we had the ability to move bugs between projects, then we'd probably set up an inkscape-reporter project to capture public bug reports before moving real ones to the inkscape project itself.Thanks so much for your help,Best Regards, Martin Owens
请登录后发言！
