• High
    • Fixed bugs for TM Maintenance

       

      1. No separate roles for TM Maintenance (all clients) and TM Maintenance (selected clients)

      2. In the new GUI there is no possibility to filter by client (bad for PM users)

      3. and some columns to select appear empty

      4. In the result table some columns are empty, too

      5. document name and additional info is shown per default (should be hidden)

      6. Edit icon in source column will open target segment to edit

      7. Adding a segment pair saves creator "none"

      8. Usability: pressing enter should start search (agreed on that to not do it)

       

      9. Usability: Segment should be fully visible:

       

       

      10. Usability: Add mouse-over for edit icons

       

       

       

      11. Usability: Give search result like "271 segments found" ideally even the total segment number: "271 segments found"

       

      12. the cursor jumps in the opened segment and delete key does not work

       

      13. editing+saving a segment will not update the author nor creation date

       

      14. add a column on the left with segment number (number of result 1, 2, 3 etc)

       

      15. add column but hide it per default with segment ID

       

      16. Use document name "TM Maintenance" for added translation units (not "none" as in initial conception)

       

      17. On saving changes in a translation unit, query the time stamp of the same ID translation unit and if it is younger then the current time stamp given in the results list (meaning the segment has been saved in a task or in another TM Maintenance), saving is not possible and give error: Changes cannot be saved.... need to think of text

       

      18. Search for empty author returns 112 segments, but in Total found segments it says 0

       

       

       

      19. Results of found segments is 261 but after Segment 200 one cannot scroll further down

       

       

      20. in TM ID 45 the search for author BORNHÖFFT does not return any segments, but there are lots. Until BORNH it will find them, sth with Umlaut Ö? The same with author "Först" in TM with ID 46; same with "ö" in source segment

      t5memory issue, will be fixed in next build

       

      21. a) It is possible to give a user "TM Maintenance" rights only, but this leads to error after login (make Editor preselected then) b) if TM Maintenance selected clients is checked, to select a client should be mandatory c) all clients and selected clients can both be checked at the same time

      Now it behaves the same as term portal roles (except one thing that I don't know yet how to fix: if tmmaintenance is the only role selected resources folder is not accessible and frontend fail to load)

      moved to https://jira.translate5.net/browse/TRANSLATE-4242

       

       

      22. User text has to be changed, affects TM Maintenance, too (just add to list)

       

       

      23. Now only 1 Segment is shown, but results are more

      This is because of missing segmentId, will be fine after reorganize is fixed on t5memory side

       

       

      24. The only column by which you can group the results is ID, which does not make sense. Makes sense for source, target, author, document name

      no, now no column at all can be grouped

          [TRANSLATE-4031] Enhancements/bugs for TM Maintenance

          Aleksandar Mitrev added a comment - - edited

          Client specific header talk with aleksandar 

          How should look like:

          InstantTranslate, TermPortal and Maintenance should share same header. Possible solution: header.phtml from where the content will be loaded and also client specific customizable.

          Role-based  navigation buttons between the components (currently possible termportal - instanttranslate )

          To check if still the case:

          • custom html content loaded per config in the header. 

          Aleksandar Mitrev added a comment - - edited Client specific header talk with aleksandar   How should look like: InstantTranslate, TermPortal and Maintenance should share same header. Possible solution: header.phtml from where the content will be loaded and also client specific customizable. Role-based  navigation buttons between the components (currently possible termportal - instanttranslate ) To check if still the case: custom html content loaded per config in the header. 

          Axel Becher added a comment -

          Technical Note about window-management:

          • the TM-Maintenance should open in an own tab
          • When opened from t5, it should only be possible to open just one instance
          • The app should be openable standalone and needs a login then

          Axel Becher added a comment - Technical Note about window-management: the TM-Maintenance should open in an own tab When opened from t5, it should only be possible to open just one instance The app should be openable standalone and needs a login then

            leonkiz Leon Kiz
            sylviaschumacher Sylvia Schumacher
            Aleksandar Mitrev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: