We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.
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.
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.
Ability to copy and paste screenshots into an incident, request, and changerequest.
John_Beasley
Customer IT Monkey ✭
Be able to copy and paste screenshots directly into either the description or a custom field in the cireson portal.
3
Comments
There are some caveats to this, though. The short version is that you would have to create your own custom field in place of the out-of-box fields to really accomplish this effectively, IMO.
Making this change to the form puts HTML into the field instead of just text. That means all the associated formatting tags eat into your character limit. e.g.: <strong>something important</strong> takes up 36 characters instead of 19.
Want to add images? Fine, but if they are embedded rather than linked, they will be base64-encoded into the text, and that will eat up a TON of your available characters.
The KB editor gets some efficiency by storing the contents of the field as binary, rather than varchar(4000). If you want to use the out-of-box service manager fields however, you are stuck with the data type Microsoft gave them (with the "Description" field--custom can be what you need it to be).
You also need to consider if anyone will be using the console (they would see a bunch of raw html unless you customized the XAML form appropriately) and how this will look in ticket reports.
With all these caveats in mind, maybe it still makes sense for you to do this. Maybe your descriptions are short enough and you have enough control over how your ticket properties will be viewed that this will be OK. I could only see this gaining traction on a custom field though. But it could be done, either by you or by Cireson.