Kelvin Posted November 8, 2016 Share Posted November 8, 2016 Since upgrading to the latest SM patch when logging a ticket and typing in the description field the cursor jumps up to the Summary field. I have tested this on multiple request type. This only seems to happen on the 'Request Details' form. Link to comment Share on other sites More sharing options...
Martyn Houghton Posted November 8, 2016 Share Posted November 8, 2016 @Kelvin I can replicate this on our system as wel in 2.36.3l, but only if the request details for is after the Service Selection or if I go back to edit it in the Progressive capture trail. Not sure if they helps with a workaround until it is fixed. Cheers Martyn Link to comment Share on other sites More sharing options...
Kelvin Posted November 8, 2016 Author Share Posted November 8, 2016 Thanks @Martyn Houghton I will take a look. Link to comment Share on other sites More sharing options...
Guest Ehsan Posted November 8, 2016 Share Posted November 8, 2016 Hi @Kelvin, @Martyn Houghton, We are aware of this issue and we are proactively looking into it. As pointed out by Martyn, we have only been able to recreate this issue in Request details Progressive Capture form. I will update this post as soon as we have a fix. Thanks, Ehsan Link to comment Share on other sites More sharing options...
Guest Ehsan Posted November 8, 2016 Share Posted November 8, 2016 @Kelvin, @Martyn Houghton, We have fixed this bug in the Service details Progressive Capture form. We are currently preparing an update to the Service Manager app, which will include a fix for this issue. Thanks, Ehsan Link to comment Share on other sites More sharing options...
nasimg Posted November 8, 2016 Share Posted November 8, 2016 Good news about the potential fix but I have to ask how was this tested as it looks like the basics of logging an incident (service requests look ok) was not done. This is also affecting us. Link to comment Share on other sites More sharing options...
Keith Posted November 9, 2016 Share Posted November 9, 2016 I experienced this same issue this morning after upgrading to 2.36.4. Strangely, closing the tab I was using (in Chrome) and opening a new tab seemed to resolve the issue. Link to comment Share on other sites More sharing options...
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