Just an example...

of what I have been dealing with:

Rex
Tuesday, October 25, 2005 9:40 PM

Is it necessary to enter a reason for every daily entry in TIMEnX?
What about normal daily entry?

The Large Company
Wed 10/26/2005 9:35 AM

It is only necessary to enter a reason if you are late (or early) - ie, past noon on the following day. For example, if you didn't input Monday's time before noon yesterday, then you would have to enter a reason why you're late. The Defense Contract Audit Agency (DCAA) requires us to submit our time daily. For this reason, TIMEnX has been structured to require a reason when the submission is late or early. If you submit each day, however, then you don't have to provide a reason. When you project time to meet the submission deadline, you will have to provide a reason as well - and it's one of the options in the drop-down menu. Please let me know if you have any further questions.

PS Adding a comment for on-time submission isn't bad. Don't worry if you've done that already.

Rex
Wednesday, October 26, 2005 10:21 AM

I will re-try the system tonight when I get home. The reason I e-mail is because when I entered my hours yeterday I was not able to hit the 'OK' button without entering a reason.

Now there are a couple reasons why this may have happened:
(1) I had not yet entered my time from the day before and was required to submit a reason there. So maybe the system thinks I need to submit a reason for everything I enter if I have to submit a reason for one thing? In which case the logic of not having to enter a reason for the current day would be false based on this pre-exhisting condition. If this is true, either the explination on how to use the system should change or the software itself should always allow one to enter a current days hours without a reason.

(2) My login could be buggy and in that case TIMEnX always needs a reason from me.

There may be more reasons, but I have work to get done.

Bottom line is I went to enter my time yesterday and I had to provide a reason.

The Large Company
Wed 10/26/2005 10:23 AM

Since you're on your way out, I wouldn't worry about this too much. You're not the only person who has had this issue, although it isn't common. It's not worthwhile to open a trouble ticket to get it fixed. Thanks for the feedback, though. I'll be sure to keep an eye out for this sort of thing.

--------------------------------------------
In closing:
1. It's Broke
2. This is how it works
3. No, it's broke
4. It's not worthwhile to fix it, I might even see it again

And I have PLENTY more examples, look for them in the days to come...
8