Under Community Review

Setting a priority looks great, but what if people always set the priority to high because their work is in their opinion the highest priority it defeats the purpose.

Should we always create a new job with medium priority and you can later give the translation job a higher priority?

How can we guide the user to select the right priority?

Translation Manager - Allow Users to set a retrieval 'priority' on a Translation Job [ROUND 2]

Among Job A, Job B and Job C, I want Job A to be picked up by the Translation Manager service first when retrieving jobs, however Translation Manager does not have the possibility to prioritize the retrieval phase.
Such feature would be very handy!

Ideally, this should look like that:

Prioritize a Job on Retrieval

and

Translation Job Queue

Parents
  • ------------
    Setting a priority looks great, but what if people always set the priority to high because their work is in their opinion the highest priority it defeats the purpose.
    Should we always create a new job with medium priority and you can later give the translation job a higher priority?
    How can we guide the user to select the right priority?
    ------------

    We definitely need to give a feature that helps to moderate the priority.
    Setting all to "Prioritized" is naturally not the meaning and the one that misuses (abuses) the feature will not see any benefit.

Comment
  • ------------
    Setting a priority looks great, but what if people always set the priority to high because their work is in their opinion the highest priority it defeats the purpose.
    Should we always create a new job with medium priority and you can later give the translation job a higher priority?
    How can we guide the user to select the right priority?
    ------------

    We definitely need to give a feature that helps to moderate the priority.
    Setting all to "Prioritized" is naturally not the meaning and the one that misuses (abuses) the feature will not see any benefit.

Children
No Data