Allow Calculations to Reference the Project's Schedule

[#1]

I've recently discovered when using calcualted data expressions, such as WORKMINUTESDIFF, in text mode reporting or in calculated fields, the calculation references the instance's default schedule rather than the schedule associated with the project you're reporting on (or the project that the task/issue you're report on is in).

Example:

This formula in a calculated field was using the default schedule

WORKMINUTESDIFF(Project.Converted Issue Entry Date,Actual Completion Date)

In order to account for the time zone and holidays of a project for one of our EU teams, I have to include the schedule ID as part of the formula in this way:

WORKMINUTESDIFF(Project.Converted Issue Entry Date,Actual Completion Date,"61858bd400325ef77ff7f86977d0b5ae")

[#2]

I have also run into this issue when calculating an individual's PTO usage as it uses the Default Schedule instead of the user's assigned schedule. As someone who is responsible for users on every continent (Antarctica aside) you can imagine the dozens of schedules and possibilities I have to account for.