Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-2314

Be able to lock/unlock segments in the editor by a PM

    XMLWordPrintable

Details

    • High
    • Hide
      Wording and Icon changed: Introduced a new processing state "locked" with a lock icon. This segments can be locked / unlocked by PM users. The processing state blocked remains for segments which can not be unlocked by PMs.
      Show
      Wording and Icon changed: Introduced a new processing state "locked" with a lock icon. This segments can be locked / unlocked by PM users. The processing state blocked remains for segments which can not be unlocked by PMs.
    • Hide
      The project-manager is now able to lock and unlock single segments (CTRL+L).
      A jump to segment is implemented (CTRL+G).
      Bookmarks can now be set also on just a selected segment, not only on an opened one (CTRL+D). Locking and bookmarking can be done in a batch way on all segments in the current filtered grid.
      Show
      The project-manager is now able to lock and unlock single segments (CTRL+L). A jump to segment is implemented (CTRL+G). Bookmarks can now be set also on just a selected segment, not only on an opened one (CTRL+D). Locking and bookmarking can be done in a batch way on all segments in the current filtered grid.

    Description

      The project manager will be able lock or unlock segments in translate5s editor for linguists, that work on the task.

      He/she will be able to do that any time, when he is able to open a task for editing.

      He/she can

      • lock/unlock single segments with a click/keyboard short-cut
      • lock/unlock all segments in the current filter set of translate5

      If the task property "Edit unchanged 100% TM matches" is changed, the single settings of each affected segments are overwritten. So if a PM chooses to unlock a locked 100% match, and another one changes the task property unlock and then lock again, the previously unlocked segment is locked again.

      If a segment is locked, because it has already been locked in the imported (sdl)xliff, it will NOT be possible to unlock it by the PM. To communicate the difference for processing status for those segments a new processing status "locked in imported bilingual document" will be introduced and the PM will get an error message, if he tries to make those segments editable.

      The changes are not reflected via messagebus to other users working on the same task. They get the changed segments when the grid refreshes. Collisions should be very unlikely, since only PMs are (un)locking.

      Attachments

        Issue Links

          Activity

            People

              tlauria Thomas Lauria
              marcmittag Marc Mittag [Administrator]
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: