Multiterm 2022 SR2 - 17.2.2.2737 did not fix the defect "Default Layout" - ENTRY NOT SAVED!

I installed, today, on November 28, 2023, the new Multiterm 2022 SR2 - 17.2.2.2737, but unfortunately the new Multiterm 2022 SR2 - 17.2.2.2737 did not fix the defect "Default Layout" - ENTRY NOT SAVED!
On 18/10/2023, Bogdan Vadean wrote: "This is a defect already logged on our side for our colleagues from development to investigate ( CRQ-35707) that occurs in MultiTerm 2022 SR1 CU2."

Why the Development Team did not fix the said defect "Default Layout" - ENTRY NOT SAVED?

The Trados/MultiTerm is a very expensive software, including a very expensive 
Level 1 Desktop - Support and Maintenance Agreement, that should provide an improved software without several defects.

Thank you very much for your kind attention.



.
[edited by: Paul at 2:22 PM (GMT 0) on 28 Nov 2023]
emoji
Parents
  •  

    Why the Development Team did not fix the said defect "Default Layout" - ENTRY NOT SAVED?

    The development team have to work through the priorities of things for a release that they can resolve within the time between updates.  The decision not to fix a particular defect, such as 'Default Layout - ENTRY NOT SAVED' immediately, is typically based on a comprehensive evaluation of factors such as the bug's severity, user impact, resource limitations, alignment with product strategy, technical complexity, availability of workarounds, customer feedback, regulatory considerations, and interdependencies with other software components. This process is complex and takes quite some organisation by the product owner and product manager who do their best to ensure that the development team's efforts are aligned with the overall goals and constraints of the project while striving to deliver the release with as many things resolved as possible.

    As far as I can see this particular bug was only logged last month and would have almost certainly avoided the planning that goes into these releases since it's also a lower priority severity as well.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Reply
  •  

    Why the Development Team did not fix the said defect "Default Layout" - ENTRY NOT SAVED?

    The development team have to work through the priorities of things for a release that they can resolve within the time between updates.  The decision not to fix a particular defect, such as 'Default Layout - ENTRY NOT SAVED' immediately, is typically based on a comprehensive evaluation of factors such as the bug's severity, user impact, resource limitations, alignment with product strategy, technical complexity, availability of workarounds, customer feedback, regulatory considerations, and interdependencies with other software components. This process is complex and takes quite some organisation by the product owner and product manager who do their best to ensure that the development team's efforts are aligned with the overall goals and constraints of the project while striving to deliver the release with as many things resolved as possible.

    As far as I can see this particular bug was only logged last month and would have almost certainly avoided the planning that goes into these releases since it's also a lower priority severity as well.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Children
No Data