How can we improve our translation site?

When restarting translation, users can't see which messages they've edited

the previously submitted by users changes are not visible so they have to remember which messages they've edited to skip them.

41 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Dimitar TsonevDimitar Tsonev shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    4 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • OliverOliver commented  ·   ·  Flag as inappropriate

        I'd like to second this idea. I usually try to group changes together. E.g. edting terminology-wise strings as one batch, then publish (with a helpful comment), then go on.

        Of course as they're still "to be reviewed" they will show up and I have no idea if I edited them already. Often happens with lots of searching and filtering.

        So any marker of "published and under review", optimally together with the string I've submitted, would be *very* helpful!

      • Dimitar TsonevDimitar Tsonev commented  ·   ·  Flag as inappropriate

        My bad, I thought that if I logout, my current changeset will be lost, that's the reason I reacted this way. However, allowing users to see their previous edits (from waiting changesets) can benefit their experience and will save their time.

      • Dimitar TsonevDimitar Tsonev commented  ·   ·  Flag as inappropriate

        Well, at the end of the day/when my time is off, I submit the changes I made. Next time, when I return, I can't see what's already submitted and what needs my attention.

      • Richard WhiteAdminRichard White (CEO, UserVoice) commented  ·   ·  Flag as inappropriate

        Do you mean that you submit a changeset and then go to make more changes and it's not obvious which ones you've already covered? If so, then why not just create one changeset? Thanks for your help in making this better.

      Feedback and Knowledge Base