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

split the current single autostate up to a composed state out of three parts

    XMLWordPrintable

Details

    • New Feature
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      Currently the autostate is one single value. For a flexible and still administrable workflow it will be necessary to change this. In fact the autostate is composed out of three values:

      1. the action which happened (edited, unchanged, restored from history, and so on)
      2. the workflow step where the action occured (lectoring, proofreading, MRC, byPM, etc)
      3. the autoflag (should be renamed to "repetition"), which is true if edit was triggered by repetition editor.

      The icon and text of the state can then be assembled out of this three values. By this dynamic combination we don't "forget" some states as its actually the case with the "translator" states.

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. TRANSLATE-416 Perfectionate QA-workflow: Flexibly organize QA-workflow with translate5 and be able to integrate whatever automated Quality Checker or manual steps whenever you want in the workflow

          • Done

          New Feature - A new feature of the product, which has yet to be developed. TRANSLATE-211 Workflow nach SAE-J2450 and additional corresponding tasks (with flexible workflow)

          • Done
          relates to

          New Feature - A new feature of the product, which has yet to be developed. TRANSLATE-202 drag down segment meta data on alternative level

          • Done

          Activity

            People

              Unassigned Unassigned
              tlauria Thomas Lauria
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: