|
The Field Controls
page is used to enforce and/or restrict field information.
All control properties are set for each group, allowing
different levels of access for different roles of users.
The mandatory setting forces users
to enter data in a specific field. This option adds an
exclamation image in front of a mandatory field so that
it is obvious to the user. If the user does not edit the
field, they are presented with an error message and must
hit the back button.
There are two classifications of the
mandatory setting. The Yes option forces
a user to submit data when a new issue is created. This
is useful to ensure that users add enough information
for a new issue and do not accidentally enter the default
setting, or leave an important field blank. The Always
option takes the functionality one step further,
by ensuring that data is entered at every step. This is
extremely useful for the AssignedTo field
so that the correct person is sent the notification on
every update. Without this setting, an updater may forget
to change the user name and the notification may never
be sent.
Field data can also be restricted by
groups, using any of the following options:
- The Read/Write option
is the default for all editable fields. This option
allows a field to be read and modified on any update.
- The Read Only option
restricts a group to reading privileges only.
- The Hidden
option hides a field from a group on all screens.
Notes:
- Access to common issues can be
controlled by projects. This is set up in the group
definitions. Groups are only allowed to see issues
that belong to projects that are visible to that group.
If you require more complicated restrictions, the Workflow
feature allows you to define controls on specific filter
criteria.
|
