Due Date Inconsistency in Engineering Change Orders

[Anonymous]

Hello everybody,

Working with Engineering Change Orders, I could see that some of them had a Due Date older than submitted date as you can see in the attached image.

I don't understand why it happens. It's so strange. Somebody have some idea of this issue?

Thank you!

[minkd]

There is no logic attached to the Due Date, it is just a value that can be set to whatever you want. The submitted date is recorded at the time the submit action is invoked.

-Dave

[steveh3]

FYI...the due date can only be modified in several stages. I know one for sure one is the "Open" state and I believe you have to be Change Admin to edit it. Often we have to manipulate the date throughout the life of a change. Thus, you must withdrawn from the Work state to the Open state in order to change it. Then put it back to the Work state. I wish that the Change Admin had the ability to edit at any state, but it doesn't.

[Anonymous]

Well, I understand that. However, I don't understand why there is a gap of 32 days between Due date and Date Submitted as show the image. I have tried to reproduce it, but I couldn't. If I also try to change the Due Date for a date before Date Created, it isn't possible.
Thanks again.

[steveh3]

What's weird, mine has always defaulted to the day you submit it. I would like to have the 30 days as a default. There's got to be a setting somewhere, although....I couldn't find it either.

[cbenner · Accepted solution]

There is no default setting for Due Date that I am aware of.  The due date is at least the creation date of the ECO, but the "Submitted" date changes each time the ECO is submitted to the next step, so it logically could be a gap of 30 days or more, depending on how long it has been in the system.