Staff -> Ability to set staff as inactive

[bswift]

Why is there an enabled column in this table when it isn't being used? We can't disable a user!

The main reason we want to disable users is to clean up our "Owners" (ie Staff) list in the dropdown when assigning tickets.

Also, this does not sort alphabetically which is kind of silly.

I don't know if this next point is worth it's own thread, but I'm wondering when the migration to MySQL 5 is going to happen (so we can create views for reporting), and when eSupport v4 (with MSSQL support) is estimated to be released?


If the enabled/disabled user thing is scheduled to be included in a future release already, can you please tell me the date for the expected release? Can you also tell me the expected release date for v4, as well as support for MySQL 5.

If release dates aren't known, could you give me a rough guess, or range of dates? I won't hold you to them, just looking for a rough idea.

Thanks.


Brett

[bswift]

I'm awaiting a response from my questions on this thread so I can decide whether I want to make some changes to the existing users, or just wait for a patch to be released.

Please let me know when the requested fixes are going to be released, or if you don't know please let me know that too.

Thanks

[Jamie Edwards]

Hi bswift,

I am afraid you should not expect a reply for at least a couple of weeks now (and even then, any decided implementation may only come in V4 and not V3).

Best,

[NC Software]

We have various sub-contractors that work from time to time. While they are not working we don't want them bothered by tickets/e-mails. I'd like the option to set a Staff as INACTIVE (checkbox) so they do not get bothered but we don't have to delete them out of the system either.

[Varun Shoor]

Should the ability to login be there or you want to disable that too?

Regards,

Varun Shoor

[craigbrass]

I think that is the point Varun. They should not be permitted to login if they are set to inactive.

[NC Software]

Correct, they should not be able to login. They would be considered laid off if you will, i.e. not employed but can come back later. We don't want to delete staff, we want to keep a record of all staff and just set them to inactive until they come back or they can remain in this status.

[Jamie Edwards]

Implemented in Version 4.

[dankinit]

Not sure if this is related to setting somebody as inactive or a new feature request. Can we have the ability to not display/not display a user in the list of users? For instance, we have a number of users who handle tickets. But we also have a few people with access, such as somebody in marketing, but we don't want them displayed on the list of users. They would still have their own login but never have tickets assigned to them, almost like a read-only access for those users. Is this possible?