HGrigsby Posted July 16, 2020 Posted July 16, 2020 Changes logged today aren't showing the Impact on the change when it is logged. This was working OK yesterday. The impact assessment, though completed, doesn't show in the timeline either on changes logged today. We had an update to the latest build last night thanks Helen
HGrigsby Posted July 16, 2020 Author Posted July 16, 2020 Have a logged a support call but this is really critical for us. Because we can't see what the impact or authorisation stage is on the change requests raised today we have had to escalate to a P2
Guest Ehsan Posted July 16, 2020 Posted July 16, 2020 @HGrigsby, The development team are looking into this as we speak. We'll apply a patch to your instance tomorrow. I will update this post once when we've applied a patch to your instance. Apologies for the inconvenience this has caused.
Izu Posted July 17, 2020 Posted July 17, 2020 @Ehsan, Please, could you confirm when this patch (mentioned in your correspondence above) will be implemented. Resolving this issue is critical/urgent for out IT department as raising CRs has now been kept on-hold. Rgds, Izu
Guest Ehsan Posted July 17, 2020 Posted July 17, 2020 @Izu, @HGrigsby, We're testing the patch at the moment. We will get this on to your instance very soon.
Deen Posted July 17, 2020 Posted July 17, 2020 For anyone else who may be experiencing this problem. The patch in question will be deployed to all instances.
Guest Ehsan Posted July 17, 2020 Posted July 17, 2020 @Izu, @HGrigsby, All, We have now deployed the patch to all instances. Ehsan
HGrigsby Posted July 20, 2020 Author Posted July 20, 2020 Hi @Ehsan Although we have the impact now showing we are missing a lot of entries from the timeline meaning that our change process is still unusable. Would really appreciate an update on this. Helen
Deen Posted July 20, 2020 Posted July 20, 2020 Our developers have completed work on a patch and this will be deployed to all instances shortly. I'll advise here when this has been done.
Deen Posted July 20, 2020 Posted July 20, 2020 The patch has now been deployed to all instances so this particular problem should no longer be occurring.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now