What are the TMS v12.5 fixes & improvements made available via CU11 through CU24?

                                                 ↓TMS 12.5 Cumulative Updates↓

CU11:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu11
CRQ-22035        Deadlocks for pre-processing tools that create many tasks are now mitigated
CRQ-21988        The drop-down arrows that indicate more information are now visible in the inbox and in archived jobs
 
CU12:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu12
CRQ-22035        Further improvements to mitigate deadlocks for pre-processing tools that create many tasks
CRQ-22146        PerfectMatch will only consider available tasks, thus preventing recoveries in pre-processing
CRQ-22200        When creating a job, the TM Filter and TM Attribute tabs will now correctly display the TM name
CRQ-22266        The source and reference files for a job are no longer switched for some jobs
CRQ-22267        Legacy file types no longer cause multiple processes on the server resulting in RAM issues
CRQ-22269        Problems with determining the correct vendor cost model have been mitigated
CRQ-22270        Creating a job with reference material that is not a supported file type for translation no longer creates a job with no files
 
CU13:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu13
CRQ-4788           Jobs that have special characters in the job name can now be downloaded from the job summary page
CRQ-5488           Creating integration jobs when the source file has an apostrophe now works correctly
CRQ-12834        Leading file name spaces are now preserved by SDL TMS
CRQ-21092        The word counts for Passolo bundles are now consistently calculated
CRQ-21338        Spaces are now handled correctly by the DITA filter
CRQ-22308        The Project TM is created correctly even when the TM contains empty custom fields
CRQ-22515        Navigating back to the search results no longer generates a 404 error
 
CU14:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu14
CRQ-22549        Custom service plugins are now routed to the correct queue
CRQ-22612        Terminology matches are correctly highlighted when the segment contains many matches
CRQ-22774        When a vendor add costs to a job, the total costs are now calculated correctly
CRQ-22889        Customizations that add multiple tasks for a single item generate the correct workflows for each task
 
CU15:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu15
CRQ-21511        Additional file types added to the configuration now have the correct encoding set
CRQ-23301        Go To Job/Task now executes when the user presses Enter
 
CU16:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu16
CRQ-23695        Cost formulas that are in use in multiple locations can fail to load
CRQ-23698        Jobs created through the CTA API will now respect the default associations
 
CU17:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu17
CRQ-23987        Federated users with multiple SDL ID logins are now supported correctly when logging in to TMS
CRQ-24018        TMS systems with large numbers of vendor projects now allowing editing the vendor without incurring a timeout
CRQ-24124        Downloading a TM from the Inbox page no longer generates an empty ZIP file
 
CU18:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu18
CRQ-22330        Uploading a Trados Studio return package no longer generates an error about the filename being incorrect
CRQ-24146        Editing a configuration does not reset the encodings to "Default"
CRQ-24162        The job quote report now displays the correct TM Leverage values
 
CU19:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu19
CRQ-24346        Integrations that specify a workflow no longer cause an error
CRQ-24430        TMS API calls will not return null values for undefined fields
 
CU20:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu20
CRQ‑22719     Searching for and then opening and archived task no longer gives a "bad request" error
CRQ-24319     Terms such as "lt", "gt", and "amp" no longer cause problems in the online editor
CRQ-24633     During pre-processing on heavily loaded implementations, the possibility of getting a "file exists" error has been mitigated

CU21:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu21
CRQ-24718     Files that are no longer available for download do not prevent the My Downloads page from loading
CRQ-24722     Files submitted for translation with non-ASCII characters in the filename are correctly processed
CRQ-24772     PerfectMatch can correctly leverage translations from ITD files

CU22:  https://community.sdl.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu22
CRQ‑23666     Reports that take a long time to generate no longer generate error messages
CRQ‑24633     Pre-processing race conditions have been mitigated to prevent AlreadyExistsException errors
CRQ‑25267     Terminology that resembles XML entities no longer causes the translation interface to fail
CRQ‑25659     The repetition word count is now calculated consistently
CRQ‑25855     Reference files are classified as job-specific when using SJP

CU23:  https://community.rws.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu23
CRQ-26398    Implementations that have reached over 4 billion target segments are no longer blocked

CU24:  https://community.rws.com/product-groups/translation_management/tms/b/sdl-tms-12-5/posts/sdl-tms-12-5-cu24
CRQ-26653    Word counts are now consistent between the Job Quote report and the linguistic analysis