I don't know if it is possible, but it would increase the user experience a lot if it is possible to redirect to the configuration overview if a build is already gone. So when someone follows a link to a build which does not exist anymore may be a good idea to redirect to the configuration and show only a hint that the build is already gone.
Maybe if it is not possible because the build is already gone from the database then store the old id in a new table pointing to the configuration and clean the table after some time. As this should not be that much data to store it should suffice to remove build ids older than 6 months or so.
Thanks
Description
I don't know if it is possible, but it would increase the user experience a lot if it is possible to redirect to the configuration overview if a build is already gone. So when someone follows a link to a build which does not exist anymore may be a good idea to redirect to the configuration and show only a hint that the build is already gone.
Maybe if it is not possible because the build is already gone from the database then store the old id in a new table pointing to the configuration and clean the table after some time. As this should not be that much data to store it should suffice to remove build ids older than 6 months or so.
Thanks
The benefit would be that build links which may be added to issue tracking still show some context what kind of build was related to the issue although the build was already cleaned.
AlSt[19/Jan/16 12:56 PM]
The benefit would be that build links which may be added to issue tracking still show some context what kind of build was related to the issue although the build was already cleaned.