please find some ideas that would be useful for us. Please not that we use public group to give customers having a maintenance plan, access to our bug base; this explains some of the remarks.
They are in order of importance/wish
- Public group people shouldn't see/set the Assignee field. It contains other customers/list of developers/logins. It may provide some hint to connect to the database(they have at least the logins) and some information that should be kept 'confidential' (toher customers names).
- There should be some mail sent to admin when unsucessful login occurs.
- As a rule, more fields (version, customs, ...) should/could be defined as mandatory for public reporters (just like external).
- It would be great at some point, to 'label' a version (some kind of milestone). For example, we have now version 1; and make a 'label' on Fortress. Then some items are added/modified/.... they must/may use this label as a version (only some versions are made public); then we create a new version/release: v2 and create the label at the same time. This way all items closed between v1 and v2 are updated and we know in which version they are fixed (and could for example create an history file)
- It would be interesting to share milestone among project. We often sell several products to a customer (let's say P1, P2), we then create a milestone CUSTOMER: PROJECT, on each product (P1, P2). But they refer to the same milestone. We would then be able to see all points among all products open for a given project.
- The user list should show the licence type (web/full)
- It would be great to be able to rename admin.
That's all
Xavier