Can you (still) not set a due date per individual files?

I'm disliking Trados and this site more every time I have to use them.

From what I could see in a 3-year-old(!) question, it wasn't and still is not possible to have a due date per file.

That is an incredibly basic function. Why has it not been implemented yet?

Unrelated, but I was tearing my hair out for 10 minutes trying to create this thread. The box to ask a question didn't appear, even after I joined the group (a dumb system to begin with). Then it worked, for seemingly no reason.

I also like how the "Customer Feedback" in Studio is not actually there to allow you to give feedback, but again, to get you to "join" some nebulous program.

emoji
Parents
  • That is an incredibly basic function. Why has it not been implemented yet?

    Every feature and piece of work is prioritised through the product management team based on a number of different scoring mechanisms ranging from what we think the right strategy is for the product going forward, bugs that need to be fixed, votes on ideas raised in our ideas site etc.  This particular feature does have a few users asking for it, but not so many that it's clear we should address this with the urgency you would like to see it done.  There is an idea for this that has been there for 8 months or so (I cannot find an older one) and only 5 users want this:

    https://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/due-date-for-single-tasks-within-a-certain-project

    It's not enough for a few passionate users to want this, and it is very easy to vote.

    Unrelated, but I was tearing my hair out for 10 minutes trying to create this thread. The box to ask a question didn't appear, even after I joined the group (a dumb system to begin with). Then it worked, for seemingly no reason.

    I'm sorry you didn't see the big red banner that said this:

    Trados Studio forum page showing a notification 'You need to be signed in to post...' with a link to join.

    We did try to make this as obvious as possible but are limited by the functionality of the forum to put this where we really wanted it... right across the missile of the screen instead of at the bottom.  We hoped the red would ring to a users attention.  We are upgrading the platform next month and will revisit this to see if we can make it more obvious.

    The reason we require this is to help with our fight against spam.  Nobody likes their inbox filled up with spam and so we do what we can to protect all users from receiving unwanted email in their notifications if they are signed up to them in the forum.  So that would be part of the reason.  The other reason is that when you are signed in we now who you are and can help you more easily especially if we need to create a support case to assist you.

    Frankly I don't think this is an unusual requirement at all.  Proz.com, TW_Users etc. all require you be signed in to participate.

    I also like how the "Customer Feedback" in Studio is not actually there to allow you to give feedback, but again, to get you to "join" some nebulous program.

    It's not exactly nebulous, unless you just didn't read it?

    Customer Experience Feedback Options pop-up in Trados Studio with options to join or not join the program.

    You don't have to join and you can opt out whenever you like.  This is in fact a good way to collect information about problems that may occur, sometimes without you even realising there is one.  This also helps us prioritise which problems to fix as it makes sense to fix the ones that occur the most often.  Asking users to report problems is a very unreliable method of gaining meaningful statistics, notwithstanding the fact many users won't bother anyway unless they know they can reproduce a problem consistently.

    If you want to provide feedback we have these forums, which I think are pretty good and we are very happy to engage with anyone irrespective of their views.  My own experience of using software and trying to get help over the last 30-40 years is that this is actually quite rare, particularly as companies get larger.  We do our best to do more to listen to our customers, but as you can see from the ideas site which has been around for some 14-years I think (give or take a year... ) the number of participating voters certainly doesn't reflect the number of users we have and it never has.  The truth is its actually very difficult to get good feedback from a statistically significant number of users.  So the customer feedback option is just one way of us getting feedback without you having to report it.  I think that's a worthwhile endeavour.

    I'm disliking Trados and this site more every time I have to use them.

    You don't have to use either.  But if you do we're more than happy to engage, and listen to your criticism to try and help where we can.  Constructive and specific criticism is always best.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 7:06 AM (GMT 0) on 29 Feb 2024]
  • Well said.

    How about THE No. 1 IDEA "64-bit version of Studio" which was raised in 17 May 2017 (em, FIVE years ago!)?

    emoji
Reply Children
  • How about THE No. 1 IDEA "64-bit version of Studio" which was raised in 17 May 2017 (em, FIVE years ago!)?

    Most users have a good appreciation of their software and a firm belief that once everything is 64-bit things will be better.  But this isn't the case.  There may be some things like being able to handle larger files where it will help, but other things you expect to get from a 64-bit application such as faster speeds are not a given.  There are other processing components in Trados Studio that would be a bottle neck restricting it from taking advantage of the benefits a 64-bit system would provide.  So these need to be addressed first and this is what the development teams have been doing.  Some of these things are not trivial and with each release we see, under the hood, that we are getting closer to being able to take the step to 64-bit and make it worthwhile.

    I know it's taking a long time but there are many aspects to this, particularly around third party components we rely on that also have to move to 64-bit before we can benefit from anything we do.  But we're getting closer and are well aware we need to do it.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji