Real Issue Tracker

Currently an authenticated user needs to be based in a Issue Tracker User Folder for the following features to work:

• Ability to assign issues to
• Option to change name without having to post a new issue or followup
• User options such as switching on keyboard shortcuts and automatic login on public issuetrackers

These features must be possible for the zope authenticated users to have to. The problem is that someone else needs to be responsible for storing the memberdata (name, email, display format). Currently the issuetracker does have a data structure for mapping standard zope user folder users with a name and email. That needs to be vastly expanded.

How about developing an object that would solely be responsible for mapping acl_users with memberdata. An object of this kind should then be deployed manually by the administrator in the root of Zope or inside a Mass Container. That one could look like this:

 class MemberdataBucket(BTreeFolder2):
    def __init__(self,): bla bla

 class Memberdata(SimpleItem):
    def __init__(self, ..., ):
       self.acl_username = ...
       self.acl_userfolder_path = ...
       self.fullname = ...
       self.email = ...
       self.display_format = ...

The implication of this is quite simple:

• Issue Tracker User Folder becomes useless
• Makes it possible to connect a SQLUserFolder, exUserFolder or LDAPUserFolder to be used solely for authentication like Plone does it.

The current code should not require people to deploy one of these but we will always have to check if such an object exits.