[tde-users] Re: Migration of services - 5. bugzilla

Hi all, the fifth service on the migration list is Bugzilla. For the Bugzilla, the situation is significantly different, because we need to discuss here before any steps are taken. -- Migration status -- Bugzilla is on Tim's original infrastructure. Therefore, no one else can manage the current instance. And there are various issues that we are currently unable to resolve, such as problem with login when https is used. So it definitely needs some change. -- What needs to be done -- First of all, we need to discuss and decide whether we want to continue using Bugzilla. As mentioned earlier, TGW is now used as a comprehensive workspace. And TGW contains Issues that can be used instead of bug reports in a separate Bugzilla. There are several benefits to using Issues. Above all, Issues are well integrated into the development workflow. It also provides good comfort - for example, it is possible to use comment formatting to make it more readable and clear. At the same time, it seems like a good idea to use one problem reporting tool rather than two independent ones. If we find a consensus that there is no significant reason to use Bugzilla, we need to decide how to deal with existing bug reports. There are two options: 1) Migrate Bugzilla to a new instance, which will be locked for adding new bug reports. This can be done more easily. However, the problem remains that there will continue to be two places for users to look for problem reports. 2) Migrate bug reports from Bugzilla into Issues in TGW and then stop Bugzilla completely. Although it is likely to be more difficult to do, I think it would be a better solution. -- More ideas and suggestions? What is your opinion on Bugzilla migration? Do you have any other ideas and suggestions? Cheers