Change Details

**Feature summary** (what you would like to be able to do and where): Special:InvestigateBlock is similar to Special:CheckUser's 'get users' block form, however, it provides a arguably better interface. This would help to reduce duplication and allow CUs to continue to inspect the results on 'get users' after blocking users (as it would open in a new tab). **Use case(s)** (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution): * As a CU using Special:CheckUser's 'get users' mode I want to block users but still keep the results page open to perform further analysis and possibly further blocks **Benefits** (why should this be implemented?): Several: * Reduces duplication of features. * Makes Special:InvestigateBlock useful to CUs using Special:CheckUser * Allows the addition of links to Special:CheckUser in 'get edits' and 'get IPs' to Special:InvestigateBlock. * Reduces the work needed for T18306, T27053, T318458, T313448, T313449 and T313450 as the features will only need to be implemented in one place (currently implementation would be needed in both to make the features work in Special:CheckUser and Special:InvestigateBlock).

**Feature summary** (what you would like to be able to do and where): Special:InvestigateBlock is similar to Special:CheckUser's 'get users' block form, however, it provides a arguably better interface. This would help to reduce duplication and allow CUs to continue to inspect the results on 'get users' after blocking users (as it would open in a new tab). **Use case(s)** (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution): * As a CU using Special:CheckUser's 'get users' mode I want to block users but still keep the results page open to perform further analysis and possibly further blocks **Benefits** (why should this be implemented?): Several: * Reduces duplication of features. * Makes Special:InvestigateBlock useful to CUs using Special:CheckUser * Reduces the work needed for T18306, T27053, T318458, T313448, T313449 and T313450 as the features will only need to be implemented in one place (currently implementation would be needed in both to make the features work in Special:CheckUser and Special:InvestigateBlock).

**Feature summary** (what you would like to be able to do and where): Special:InvestigateBlock is similar to Special:CheckUser's 'get users' block form, however, it provides a arguably better interface. This would help to reduce duplication and allow CUs to continue to inspect the results on 'get users' after blocking users (as it would open in a new tab). **Use case(s)** (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution): * As a CU using Special:CheckUser's 'get users' mode I want to block users but still keep the results page open to perform further analysis and possibly further blocks **Benefits** (why should this be implemented?): Several: * Reduces duplication of features. * Makes Special:InvestigateBlock useful to CUs using Special:CheckUser * Allows the addition of links to Special:CheckUser in 'get edits' and 'get IPs' to Special:InvestigateBlock. * Reduces the work needed for T18306, T27053, T318458, T313448, T313449 and T313450 as the features will only need to be implemented in one place (currently implementation would be needed in both to make the features work in Special:CheckUser and Special:InvestigateBlock).