Broken entries reports - details in message

Hello,

Thank you for your suggestion. I'm taking note of your request. We will analyze how we could improve that. We will post here once we have an update on that.

Best regards,

Thank you very much for the quick reply, much appreciated.

Hello there,

Just a follow up if you think this will be added in an upcoming version?

Thank you again :o)

Hello,

I can't give you and ETA for now. I thought about it but I don't have an easy way to add that for now. We could add the content of the secure message in the email and you would have the broken entry detail. But for a security reason, we don't include the content of a secure message in the email. I'm wondering if we could have some sensitive data in the broken entry message. If it is the case, I'm not sure we want to add that information in an email. Do you see any use cases where you would not want to see the secure message content in your email ? Of course, we could have an administrator setting to add or not the content in the email. We still have to discuss that internaly. We will post here once we have an update on that.

Best regards,

I don't see a reason why we wouldn't want to know what entry is broken(that said, we obviously don't want to have the username/password in the email but at least knowing the entry name would be very useful).

Thank you very much for the follow-up.

Hello,

I have discussed with colleagues and one solution that we had was to add the secure message subject in the email. Would it work for you if we add the subject in the email that we send. For a broken entry, the subject could be something like "Broken entry: ConnectionName". The content of the secure message (the message from user when he reports an issue) would not be included in the email because we think that people could add sensitive data. But we don't expect sensitive data in a message subject. Does it make sense to you ?

Best regards,

That would be perfect to have this information in the subject, many thanks !

Hello,

I created a ticket and added it to our backlog. We will post here once we have an update.

Best regards

Thank you.

Hello,

Devolutions Server 2024.2.3.0 has been released. It contains an improvement for what we discussed here. Please let us know if you can try it and if it does what you need.

Best regards,

Hello there,

I have tested the improvement this morning and it works great. We see "[Server name] - Issue Report for" in the email subject.

That said, we would have prefered to see "Broken entry report for" instead of "Issue report for" as the subject, is that possible?

It is helping a lot with this improvement though.

Thank you very much!

Hello,

Thank you for your feedback. It is probably something possible. I will have a look after my vacation. Quickly, in our application, the feature is called "Report an issue" so this is why we named it that way. But I agree that when you report it, you can flag the connection as broken so it would probably make sense.

Best regards,

Hello again,

Hope you had a nice vacation. Is there an update on this modification request? :)

Thank you very much.

Hello,

Sorry for the delay. I would suggest to write "Broken entry report for" if the flag as broken is checked and keep "Issue report for" if it is not checked. Would it work for you ? The goal is just to avoid confusion between terminology. The feature goal is to report an issue, but it is true that at the same moment, we can set the broken flag on the entry and we could write it in the email subject.



Best regards,

That sounds perfect. Will this be in the next release?

Thank you very much !

Hello,

Yes, it will be part of the next release, 2024.3.2.0. It should be available next week.

Best regards,