Mistys request from issue116951:

User voice item being entered on Misty's behalf

When viewing an issue and clicking 'Print Preview' the browser provides the printable view but there is a lot of used white space.

Misty advised the unused space should be utilized better. Some ideas are as follows:
-Fields that don't contain anything should be skipped completely
-Print Preview should situate fields more closely together if possible, Instead of it retaining the look and feel of the page view in the browser.

A customer would like to have the headers on the history pop up windows, sort the column information.

Allow more than one asset be assigned to an issue

We need to use a custom defined field with dropdown values A or B.

If A is chosen we want to display another field with dropdown values 1 and 2

If B is chosen we want to display another field with dropdown values 3 and 4

we always have people calling in for other people. We would like to capture this information, with a field that auto grabs the history like caller and location does.

When entering an Issue/Ticket, currently the Organisation name is only selectable if you type the exact first letters of an existing Organisation name. Change so instead Organisations can be searched mid-string for values.
e.g. Organisation “The Learning Place (GJ Smith)” is currently only selectable if you type 'Th...'. Instead, it should be visible for selection if the user types 'Th..', or 'Lea...', or 'Smi..' etc.

A customer would like to have the ability to disable the Details links and the history Links on the issues that they enter or view. This can potentially expose data that they should not be able to view.

Add granularity for permissions for issue fields, such as Priority. If Issuetrak had the ability to control select, edit and view permissions for issue fields it would allow certain information to be kept private. I worked with Amfit inc and they would benefit from having the ability to control the view permissions of a built-in field (Priority, Severity) for certain users.

You need to add a total time by assignment so we can track how long tickets are assigned to different groups that automatically adjust for after hours and weekends.

It would be beneficial to have the ability to rename the label for Open and Closed status in Issuetrak.

Right now when you add an asset to the field it search by the asset#.

I would like to be able to modify the field that it search for the asset.

Instead of looking for the system generated asset# i want to search by the inventory# which is the number that i put on the equipment.

Do not remove text from the input fields on the portal that is allowed to be sent via email. Additionally, do not remove text that was sent via email when the description is edited.

Sample of text that is being remove alert(

Example:
Input:
Take a look at the alert(at the top of the screen)

Current Resulting Behavior:
Take a look at the at the top of the screen)

I got the idea from our Slack. Users add what slack calls reactions to comments, typically positive. This is similar to facebook's 'like it' or 'thumbs up' (whatever feature...I don't really use facebook).

Several popular blogs/support/community forums do the same thing, where they somehow flag a note/comment/response as "Verified Solution/Workaround/Resolution" stuff like that. Attached are a few examples

Allow the Issue Change log to be a selection on the user or template permissions rather than only available to licensed users.

There is currently no way to determine which quick pick was used when an issue was submitted. Adding this as a field to the database would be helpful in managing quick picks.

In the interest of keeping the submit screens as minimal as possible for end users, admins should be allowed to move or hide the submit date and time fields from employees submitting cases.

Currently these fields are hard-coded into the issue screens and are unable to be modified in any way. We feel it would be very beneficial if we could at least move these fields to the bottom of the submit screen. Ideally, we would like the option to hide these fields from those submitting issues.

Finally we are unsure as to why these fields are editable. Thanks!

When viewing an issue the text fields have a relatively small fixed width. Additionally the standard text and RTF editing windows are also relatively small and not dynamic.

The Width should be dynamic and the administrator should be able to set a fixed value.

The height should be set by the administrator globally.

The ability for user to have width/heights settings would also be useful.

It would be great if we could respond to a check box on the form, then have the response add fields or task groups to the issue after the response.

Sometimes you have an issue for someone but its sent in by another party(maybe person's supervisor), like a check box to select recorded by, and then once selected another field for user name comes up, and when notifications go out it goes to that other part as well.

I have issues that are sumitted by supervisor via email but for another person. Like both copied easily.

It would be helpful to be able to assign more than one user to an issue, in some cases some users I have worked with wanted to assign a team of users to work on an issue. By assigning individual users they can add and remove users as needed without needing to change a group membership. In some cases they might assign to a group, but also want to add additional resources on an individual basis to the issue. Using this method instead of task allows a user to see their entire workload in one place.