Index card General
Index card General |
|
|
(A) (M) ( Main menu - Settings - Edit Project - Table structure - Selection lists - General ) Define the attributes of a column
Description In the index card General you define the attributes of a column that lay down design and internal structure of the column.
Fill out the following fields: •Column caption Enter the column's name that will appear in the list view. •Position before column Here you determine the order the columns are displayed e.g. in the list view. You can put the column at start, at end (of the row) or in front of another column. •Data type Enter the data type the field will be fed with in the future. This is important for the data base to function smoothly. Apart from that, you have following possibilities: •If you choose a data type with the addition selection (e.g. text selection), a selection list will additionally appear underneath the input field containing all entries that have been made so far. •If you choose the data type attachment, you can use the field to upload files to the server and provide them for other users as downloads. •If you choose the data type selection list, a selection list will appear. You can define the content of the selection list in the view Selection lists •Multiple selection lists are also available. •The data type project member is a predefined selection list. A selection list will appear containing all members of the project. This data type carries another specific: When sending automated emails, you can choose the recipient from this selection list. •The data type link list makes it possible to put a list of references to other entries into this field. This makes it possible that connections between various references can also be organized project-overlapping •Default value You can determine if a field obtains a default value. You have following options: •Date read-only The current date will be entered automatically into the field and cannot be edited. •Date writable The current date will be entered automatically into the field as default value. In this case the value can be edited. •User read-only The name of the current user will be entered automatically into this field. The name cannot be edited. •User writable The name of the current user will be entered automatically into this field. The name can be edited. •Company read-only The name of the user's company will be entered automatically into this field. The name cannot be edited. •Company writable The name of the user's company will be entered automatically into this field. The name can be edited. •Value If the default value is of the type Value a new input field is shown in which you can enter the default value - of course only if the value is valid in the scope of the data type. Is the data type a selection list either the values of the selection list are shown or, if the selection list is not defined yet, the hint "No selection entries have been defined for this column.". After the selection list is defined the possible values are shown.
•Input required You can decide if the field is required or not. If the field is required, the issue containing this field can only be saved as long as the field has been filled out. If you decide here that a field is required, you can - in the View Status change details - decide for each status change individually if the field has to be filled out or not. •Save history If you check this checkbox, a history about the changes made to this field will be recorded. Users can view this history by clicking the histroy-icon that will appear within the field in the List view. •Internal Length (# of chars) You can determine the maximum length (number of chars) of the field in the database. •# chars to be displayed You can determine the visible length (number of chars) of the input field in the List view. •Field width in pixel You can determine the width of the column (number of pixel) in List view. •Status relation You can determine which status the column shall be assigned to. Primarily the status relation has an optical effect because the relevant column is tagged in the respective status color. Is a new column created and other columns already exist, the status relation îs set initially on the status which is tagged at the moment of creating. If the status relation is changed after creating the new column, this only has an effect on the color of the column. Write accesses on that column are still only allowed on the initial set status. To change the access on a column you have to make modifications at the Workflow permissions. •Take over in email subject Here you can define that the filed value of this columns will be taken over in the email subject line of emails sent from The standard is that no field value will be sent in the email subjects. To take over a field value please select the option "position 1". If more than one columns should be added to the email subjects, you can define the position of the field value in the email subject. Note: The email subject line is restricted to 988 7-bit ASCII characters. Non-ASCII values may be represented using MIME encoded words. In most cases you can only send about 900 characters. A lot of email software only displays about 250 characters in the email subject line. Of these reasons it could be senseless to take over long text fields in the email subject. •Email import: Fill from Here you can define which contents of an email should be assigned to this culumn content in the case of automatic email import in •Sender •Subject •Text •CC •Date •To (receiver) •Attachments If the new issue will be created from an attached XML file and this column also defined in the XML file, the content of the column is also filled by the XML file. Note: The automatic email import must be licensed. In other case these definitions will have no effect. Please compare the help to the automatic email import.
General information about the view Table structure
|
.