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
  • Seems like a logical enhancement. We have customers who can submit huge amounts of content, we should be able to prioritize how this is retrieved. As a minimum it should be based on chronological order assuming the job is ready to be retrieved. 

Comment
  • Seems like a logical enhancement. We have customers who can submit huge amounts of content, we should be able to prioritize how this is retrieved. As a minimum it should be based on chronological order assuming the job is ready to be retrieved. 

Children
No Data