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

Restrict Jobcoordinator access to workflow steps

Details

    • Improvement
    • Resolution: Unresolved
    • None
    • None
    • job coordinator

    Description

      From Vilker's issue:

      We’ve noticed that it’s possible for job coordinators to change the status of workflow steps to finished even if it’s not their turn yet.

      We have one example (where the reviewer is assigned the QA step, so the agency can check the changed in the “review” step):
      Translate (jobcoordinator): finished
      QA (editor): open
      Review (jobcoordinator): waiting → jobcoordinator changes it to finished and the whole workflow finishes.

      While it certainly is a mistake on the agency’s side to manually change their jobs from waiting to finished when preceding workflow steps have not been completed yet, do you think it makes sense to (technically) disallow this?
      Or do jobcoordinators simply need to be familiar enough with the system to not do this?

      Solution

      Restrict JC on his attempt to update job's state.

      Check for state of task and step of JC job to determine what is allowed for JC

      Attachments

        Activity

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

          Restrict Jobcoordinator access to workflow steps

          Details

            • Improvement
            • Resolution: Unresolved
            • None
            • None
            • job coordinator

            Description

              From Vilker's issue:

              We’ve noticed that it’s possible for job coordinators to change the status of workflow steps to finished even if it’s not their turn yet.

              We have one example (where the reviewer is assigned the QA step, so the agency can check the changed in the “review” step):
              Translate (jobcoordinator): finished
              QA (editor): open
              Review (jobcoordinator): waiting → jobcoordinator changes it to finished and the whole workflow finishes.

              While it certainly is a mistake on the agency’s side to manually change their jobs from waiting to finished when preceding workflow steps have not been completed yet, do you think it makes sense to (technically) disallow this?
              Or do jobcoordinators simply need to be familiar enough with the system to not do this?

              Solution

              Restrict JC on his attempt to update job's state.

              Check for state of task and step of JC job to determine what is allowed for JC

              Attachments

                Activity

                  People

                    sanya@mittagqi.com Sanya Mikhliaiev
                    sanya@mittagqi.com Sanya Mikhliaiev
                    Thomas Lauria
                    Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                    Dates

                      Created:
                      Updated:

                      People

                        sanya@mittagqi.com Sanya Mikhliaiev
                        sanya@mittagqi.com Sanya Mikhliaiev
                        Thomas Lauria
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                        Dates

                          Created:
                          Updated: