2

In the past, the "Completed Jobs" page was sorted by the date the translation was submitted/approved. However, recently, there seems to be no logic whatsoever behind the sorting algorithm of the page, making it difficult to find the jobs which were completed recently outside of the 5 listed on the recently approved page. Is there a way to bring back the old sorting method, that is, sorting by date?

11 comments

  • 0
    Avatar
    juan.garcia.heredero

    Hello,

    They are trying to solve this. Meanwhile, I made a tool so we can recover info about completed jobs. It generates a file that can be opened with Excel for instance, and you can order the results by date or whatever.

    https://support.gengo.com/hc/en-us/community/posts/245427047-New-tool-to-retrieve-info-about-archived-jobs

    https://support.gengo.com/hc/en-us/community/posts/245416287-Tool-to-retrieve-info-about-archived-jobs

    Cheers.

  • 0
    Avatar
    xicearcher

    Cool, I didn't see that tool! Thanks for developing it, but I sure would want the sort function to be restored, at least.

    Thanks!

  • 0
    Avatar
    juan.garcia.heredero

    Yeah, me too, but I just didn't want to keep waiting until Gengo fixed it. I cannot find the thread now, but I think this issue has been happening for several months now.

  • 2
    Avatar
    bert.luyten

    Yeah, I sent a support ticket about that back in October, and I was told they're working on it.

    Seems like they're working really hard, since it's still not fixed.

    In the meanwhile, the preview version is still broken too since who remembers when.

    Second payment option is apparently also super complicated to implement.

    I mean, Gengo is great, but it seems like they don't have anyone actively working on these things which have been brought up countless times.

  • 0
    Avatar
    Lara Fernandez

    Hi all!

    We've released a fix for this today and your completed jobs should be showing in the correct order (from latest to oldest) now :)

    Thanks,

    Lara

    Edited by Lara Fernandez
  • 0
    Avatar
    juan.garcia.heredero

    That's good news, Lara, thank you very much. It seems to be working ok.

  • 0
    Avatar
    kvstegemann

    Looks good! Thank you for fixing this.

  • 0
    Avatar
    Flash-Ost

    Thanks!

    BTW, was this a part of the fix or something went wrong?

  • 0
    Avatar
    kvstegemann

    I assume that this is due to the problem with the display of the word rate. There was another issue, where the word rate was not displayed correctly when a job still used the old rates. In the individual job view, this seems to be fixed too now, but in the job lists it seems as if the word rate was removed entirely. Not sure why. Now that it is fixed, it could as well be displayed.

  • 0
    Avatar
    Lara Fernandez

    Hi all!

    I will post separately later today about the reward rates so that people who are not following this specific post have access to the information as well, but yes, as @kvstegemann has noted, the reward rate display has been fixed. However, as @Flash-Ost pointed out, we have moved it to the individual job details page.

    The reason for this is that we are in the process of redesigning the dashboard and, in the new dashboard, reward rates will be displayed in the job details page only. This is the result of several user testing surveys in which the general feedback we received from translators was that they don't find the reward per unit to be a very useful piece of information to state on the dashboard, and the majority stated that they tend to focus on the total reward only.

    Thanks,

    Lara

  • 0
    Avatar
    juan.garcia.heredero

    Well, I really don't understand that change. I mean, you already have that info, so you can just display it for the translators that used it. More info is always more useful, and it's not that the user interface was messy or anything.

    Of course the majority of translators focus on the total reward, since usually the price per word is always the same for the same job difficulty (except the jobs transitioning to new reward rates). But, what if that changes in a future? What if we have, for instance, standard jobs that can be $0.03, $0.04 or $0.05 per word? Must we enter the jobs, one by one, to know their price per word?

    Another (minor, negligible) side effect is that my tool to retrieve archived jobs has stopped working because of this. I can fix it in some minutes... when I find the time (which can be in some days). At least you still show the total number of words, so my tool will just divide the price by the number of words and will store the resulting price per word.

Please sign in to leave a comment.