Make it so the "Can Log In" parameter is inherited from the Self Registration user template from which the user was created.

Reference: https://support.issuetrak.com/CSIssue_View.asp?IssueNbr=103333

It would be nice to have the ability to quickly pull up a list of users in the User Search area filtered by if they are AD Authenticated or not.

On the Change Password page to change a user's password, it prompts for "Your current password (to authorize the change)". This can be confusing for admins, as it is sometimes interpreted as asking for the password of the user for which the password is being reset. It would be helpful if the wording more clearly indicated that the current password is the password of the admin that is currently performing the password reset.

Have the ability to turn off the ability to allow end users to email. This way sensitive information does not leave the system.

Change user permissions so that End Users can be restricted to view only tasks assigned to them and not any tasks assigned to other users for an issue.

Ref support issue: https://support.issuetrak.com/CSIssue_View.asp?IssueNbr=107513

Currently, when creating a new account, an email gets sent out saying "Your account has been created, click this link to update your password". This email message is pre-determined and not editable. Create an option to edit the text of this message.

Add logging/reporting for all logins and failed login. Report could be emailed or downloaded then imported into a SIEM. Additionally add logging for password reset requests including IP address that requested the password reset.

Currently, when a user is created and sent a link to set their password, the email does not inform them of their userID. This makes them contact their support team for their userID. This is not a good practice and causes extra work and headache.

When new user accounts are created, there is an option to allow the user to set their password. However, the email generated after the account is created does not include the user id information.

Request the default 'new account' email include User Id.

Worked with Comcast and Allison Schneider regarding this feature request.

Allison asked if Issuetrak has a configuration option to change required fields when adding a caller(specifically, email address). It would be helpful to have a way to change required fields when creating new end users and/or Agents.

Existing customers maybe expecting the password boxes and have a difficult time finding the change password link.

We would like to see the Organization administrator feature returned to the product. We have a large number of Organizations that are set to private and without the Organizational Admins this puts the responsibility of creating new users on System Admins.

When using the self registration feature there is no way to properly associate the user with an organization. I would suggest adding a field to record the email domain of the organization. Multiple values would be helpful. When the user is added either through self registration or through IEM, then the code could compare this list to the email domain of the newly registered user. If a match is found then the user would be created with the matched organization. If no match is found, the default template organization would be used to create the user.

We use AD to integrate with Issue Trak. We frequently deactivate and subsequently activate users in our AD infrastructure but once the itrak sync flags the user as "deactivated" it does not automatically "reactivate" the user once we do in AD.

Create a new table User Permission History that stores a log of User Permissions.

Provide Provide Licensing Model to Support Concurrent Adv Users. For example, we could create 100 Adv Users, but limit the number of concurrent logged in users to 75% of total. Or just hard code it.

See issue 98702

At present, the permission to delete Issues and delete related attachments are combined into one permission. Requesting that these permissions be separated. I have several employees call me and ask for me to delete an attachment for them as I have elected not to provide this permission so that an issue/incident does not get inadvertently deleted.