Martin_T Posted May 17, 2017 Share Posted May 17, 2017 Hi Guys, We'veĀ noticed that some of the ticket titles from the RMM system to PSA are way too long, please check the attachment. Other events like backup failures/successes are fine but CPU and Memory usage tickets are massive. Would you be able to look into a way to create less obtrusive ticket titles from RMM? We've also noticed that the RMM priority doesn't necessarily map to a PSA priority. Is there a way to do this or is this something to come out in the future? Many thanks, Martin Link to comment Share on other sites More sharing options...
Administrators Paul Posted May 17, 2017 Administrators Share Posted May 17, 2017 Hi Martin, At this moment the priority is the same for all RMM notifications and is configurable from the PSA under the Admin -> Service Desk -> RMM Integration Settings -> Pulseway Integration -> Priority. As for the extra long notification name, yes we should definitely trim the excess there. Thanks for reporting itĀ . -Paul Link to comment Share on other sites More sharing options...
Martin_T Posted May 17, 2017 Author Share Posted May 17, 2017 28 minutes ago, Paul said: Hi Martin, At this moment the priority is the same for all RMM notifications and is configurable from the PSA under the Admin -> Service Desk -> RMM Integration Settings -> Pulseway Integration -> Priority. As for the extra long notification name, yes we should definitely trim the excess there. Thanks for reporting itĀ . -Paul Ahh brill, thanks for that, couldn't seem to find the settings earlier. I've taken a look in there and even though they are mapped, anything above Normal is also being given 'Medium' priority :-/ Any ideas? Link to comment Share on other sites More sharing options...
Martin_T Posted May 30, 2017 Author Share Posted May 30, 2017 I've fiddled about with these settings a little more and still cannot get it to behave properly. Link to comment Share on other sites More sharing options...
Staff Chris Posted June 2, 2017 Staff Share Posted June 2, 2017 It appears that this is a bug, I have notified our development team about this, therefore this will be fixed ASAP. Martin_T and Comissha 2 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