Hey? Question? How come you are changing the due date of this story? It’s done already. And it had a due date of Sept 2018, and you changed to due July of 18? Very curious.
The due date of this one is getting synced to PMCS. The due date of the milestone LDM-503-08b is 2018-09-06 (that's
DM-17118); this ticket, to write the test plan for that milestone, is automatically getting a due date 45 days before that (so late July 2018).
You're right that this is, in some sense, meaningless, since the work has already been done. But it was easier just to set the due date on all L2-milestone related tickets, rather than to try and special case those that had already been completed. Sorry if that caused confusion!
And…. How come a due date was changed on a story for the L1 deployment of a GPFS appliance in Chile? We don’t usually due dates? So this story is the config of the unit… not the deployment in chile and is completed. The work for the deployment will be starting soon and we have other epics and stories for that work. Should we be using due dates? We use start and end dates for tracking earned value epics. Are we doing something wrong here?
I'm not sure what you're referring to here. This ticket isn't about a GPFS appliance in Chile. Is that another ticket? If so, it's probably a typo on my part (I transcribed all the ticket numbers referring to milestones here and I might've got a digit wrong). If you can point me at the ticket, I'll fix it.