Why not have the timestamp on each ticket reply?

because people are in different timezones.

I'm sure people could be persuaded to select the time zone appropriate to them.

because people are in different timezones.

:whistle: then email shouldn't have timestamps too (w00t)

Tickets? In the Client Area?

There are currently times on ticket replies.

Tickets? In the Client Area?

There are currently times on ticket replies.

I don't see it anywhere. :unsure:

I don't see it anywhere. :unsure:

It says at top of ticket 1HR open, Ten Mins awaiting customer action etc etc etc :)

It says at top of ticket 1HR open, Ten Mins awaiting customer action etc etc etc :)

That only shows for the last reply and it doesn't show how many minutes after the hour as well.

It's really that hard to add the time to each reply? :blink:

It's really that hard to add the time to each reply? :blink:

No, it isn't hard to add. But honestly this is the first I heard of this request. But I'll be sure to alert the people responsible for the interface to review this suggestion. :)

Well I agree because if I reply and the staff's last reply was about a couple of hours ago I would like to know like 12:45 when the last activity was posted or something.

Exactly! there are many reasons when one needs to check what time the tech replied... I'm surprised no one have raised this issue until now. I don't know any ticket system that doesn't display the time on each reply.

I see that you guys added the timestamp to each reply now. :thumbsup: Great for future reference as well. One more thing, would be nice to have our names instead of the email address on each reply. :)

Thanks for making the change! :cool:

I like adding a timestamp to tickets and the user can select there time region they are in. :) If you guys really need a timestamp check your e-mail and it will show you what time you last posted and such.

The time is not set correctly even though it says EST and I'm in the eastern time zone.

But honestly this is the first I heard of this request.

I don't think that should be an excuse nor a reason to take this suggestion less serious than any of the popular ones. I've asked/suggested a few modifications to be added to IPB yet because there are modifications out for them already I don't get a say.

The suggestion side of things with IPS is a little, erm, pap / crap -- there's always an excuse or a reason for why something shouldn't be added or looked into. I thought IPS were different in the sense that they listened to their consumers but in the suggestions area (from what I've seen) you're the same as any other successful company. :(
</rant>

I don't think that should be an excuse nor a reason to take this suggestion less serious than any of the popular ones. I've asked/suggested a few modifications to be added to IPB yet because there are modifications out for them already I don't get a say.

The suggestion side of things with IPS is a little, erm, pap / crap -- there's always an excuse or a reason for why something shouldn't be added or looked into. I thought IPS were different in the sense that they listened to their consumers but in the suggestions area (from what I've seen) you're the same as any other successful company. :(

<

/rant

>

I'm sure there are suggestions you would like to see added, but that doesn't necessarily mean we can or will add them. :)

We take ALL of the suggestions made (which literally tops 1000 for any given release) and decide which would be the most beneficial to all of our customers as a whole. If you want a shoutbox added, that doesn't necessarily mean we will. But if someone says "xyz interface is a little confusing, and I think it would work better if you did abc" then it's likely that would be looked into. If 100 people reply to a topic saying they think a particular feature is useful (and it doesn't really deviate from our goals) then we'll likely look into it. But at the end of the day, remember - IP.Board is a forum, and we're starting to get to the point where every imaginable feature for a forum has been added, so people are starting to ask for things that don't really enhance the forum itself.

I'm sure there are suggestions you would like to see added, but that doesn't necessarily mean we can or will add them. :)

We take ALL of the suggestions made (which literally tops 1000 for any given release) and decide which would be the most beneficial to all of our customers as a whole. If you want a shoutbox added, that doesn't necessarily mean we will. But if someone says "xyz interface is a little confusing, and I think it would work better if you did abc" then it's likely that would be looked into. If 100 people reply to a topic saying they think a particular feature is useful (and it doesn't really deviate from our goals) then we'll likely look into it. But at the end of the day, remember - IP.Board is a forum, and we're starting to get to the point where every imaginable feature for a

forum

has been added, so people are starting to ask for things that don't really enhance the forum itself.

Can I make a suggestion for the next release then :P can you put the winning lottery numbers in a code , obviously before the draws take place :lol: :P

The suggestion side of things with IPS is a little, erm, pap / crap -- there's always an excuse or a reason for why something shouldn't be added or looked into. I thought IPS were different in the sense that they listened to their consumers but in the suggestions area (from what I've seen) you're the same as any other successful company. :(

<

/rant

>

I agree with this in terms of software features for IPS, you often hear things like "this would be hard because of *technical reason*" when a customer, who most likely doesnt have in depth technical knowledge (if they did....they would try it themselves as a modification) does not want excuses they just want a "we will look into it" or "thanks for your suggestion we will keep it in mind".

Sure, but if you say things like that, them people tend to expect that it (whatever it is) will be possible/added in the future. I don't think that their technical reasons go too far beyond comprehension. It isn't like they start talking in bytecode or anything related to php functions. Typical reasons given are "large increase to server load" and "software incompatibilities". As a customer, though I may not understand exactly what server load is beyond "usage", I can understand "software incompatibilities" and I would prefer to know that something is NOT going to be added rather than to have been dragged on for months or years with "will look in to it" or "thanks for your suggestion. We'll keep it in mind".

Sure, but if you say things like that, them people tend to expect that it (whatever it is) will be possible/added in the future. I don't think that their technical reasons go too far beyond comprehension. It isn't like they start talking in bytecode or anything related to php functions. Typical reasons given are "large increase to server load" and "software incompatibilities". As a customer, though I may not understand exactly what server load is beyond "usage", I can understand "software incompatibilities" and I would prefer to know that something is NOT going to be added rather than to have been dragged on for months or years with "will look in to it" or "thanks for your suggestion. We'll keep it in mind".

I've gave my feedback - I don't want excuses :P You are giving excuses stoppit! :P

If they are not going to implement it, then they could just say "sorry, it is not possible at this time, thank you for your suggestion however, if it is possible for us to implement this in a future version we will look into it again" etc.

I've gave my feedback - I don't want excuses :P You are giving excuses stoppit! :P

:lol:

If they are not going to implement it, then they could just say "sorry, it is not possible at this time, thank you for your suggestion however, if it is possible for us to implement this in a future version we will look into it again" etc.

Agreed, some middle ground I suppose :P

Sure, I'll gladly say no without giving a reason if that's what you prefer. :) I just figured more people than not would rather have some sort of reason other than "No, not at this time". But your way will save me reply time. :P

If 100 people reply to a topic saying they think a particular feature is useful (and it doesn't really deviate from our goals) then we'll likely look into it.

Yet I'm sure if one big company like Sony, Nasa, AMD, Yahoo and all the other big companies (just one) were to suggest something you'd most probably consider it. Not to mention if 3 (at most) were to agree/suggest the same thing... yet it'd take 100 or so regular users just to get something considered.

I guess money does speak volumes, but going back to what has been said in another topic: you try to treat everyone the same :shifty:

Point of this post is that, you appear to not consider what the minority want and that minority should be valued customers not just another figure. That's where other companies go wrong, I thought you guys were different >_< . I'm not saying all suggestions should be considered just sometimes a little thought or whatever wouldn't go a miss -- just because it's an minority doesn't make it any less of a valid point. </rant done [for me]>

Yet I'm sure if one big company like Sony, Nasa, AMD, Yahoo and all the other big companies (just one) were to suggest something you'd most probably consider it. Not to mention if 3 (at most) were to agree/suggest the same thing... yet it'd take 100 or so regular users just to get something considered.

What exactly are you basing this on? You have no way of knowing if "big" companies suggestions are given any more weight than anyone elses suggestions. We've inlcluded far more feautres that were suggested by our community than were suggested by our "big" customers. The source of an idea is not an issue, it's how the idea fits in with our goals for IPB, as well as a myriad of other factors that determines if it gets included or not.

Point of this post is that, you appear to not consider what the minority want and that minority should be valued customers not just another figure. That's where other companies go wrong, I thought you guys were different . I'm not saying all suggestions should be considered just sometimes a little thought or whatever wouldn't go a miss -- just because it's an minority doesn't make it any less of a valid point. </rant done [for me]>

For the most part majority rules, we have a limited time to develop a release and limtied resources, we have to make the changes that we feel benefit the majority of our customers. The larger a feature is and the longer it takes to implement, the better it has to be for the majority of our customers.

What exactly are you basing this on?

I said: "Yet I'm sure..." -- not stating fact, I'm just adding to my point. Most companies listen to their bigger customers than the little people... all linking into minority.

...meh... I get your point -- but a suggestion made by an minority might work out. All I'm saying is you should really consider giving the minority a chance. >_<