We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Change Requests - Add/Use a ClosedDate property instead of overwriting ActualEndDate
After implementing the latest Auto Close app, we discovered that when a Change request is closed, the Actual End Date is overwritten. This is a business problem for us, as logically the Actual End Date is set by the change implementer if the change end time differed from the scheduled end time, e.g. a change took longer to implement than expected.
This is a valuable metric for our reporting. At present, we can either a) not close any changes in the system, or b) accept that the actual end date will be useless for reporting purposes as it will be overwritten when the change moves to closed status.
The Change Request class does not appear to have a property for Closed Date, which I assume is why the decision was made to use the Actual End date for this purpose. However, as explained above, this is not acceptable from a business reporting standpoint.