...
Attribute Type | Description |
---|---|
String (255 chars) | For simple string type attributes such as "Phone", "E-mail", etc |
Type to store E-mail of a company | |
Website | Type to store Website address of a company |
date | Datepicker with calendar for date type attributes such as "Contact birthdate". |
number | Integer number. For example, "Number of users". |
checkbox | Single checkbox (yes\no). For example "Is platinum partner: Yes" |
list of values | Used for selecting one value from cascading list. For example, "Company type" or "Branch". Possible values should be set in attribute property "Field values". For example: "1:Client;2:Rival;3:Partner;4:Agency" |
Position | Values from Position dictionary. If there is no positions you can enter new value and save contact - new position will be added in the dictionary. |
Contacts | List of contacts related to the company. Select fields to show in Company card. You can add/edit/remove contacts here. |
Contact | This field is used for selecting main contact/contacts of the company. It is used for displaying main contact in the company dictionary or for searching company by contact. There can be several fields of Contact type in Company card with different contacts selected. |
Company | This field is used for selecting company in contact card. Contact can be related to only one company at the moment. You can enter new value here - in that case a new company will be created in the company directory. |
JQL | This table-field displays JIRA issues by JQL-filter with necessary attributes. The value must be specified as JQL-filter in attribute property "JQL condition" If you want to dispay JIRA issue where current company or contact is specified - you need to provide the following values in the filter:
Example of JQL condition: "project = SALE AND issuetype = SALE AND 'Company' = CURRENT_NAME" If you want to dispay JIRA issue where company is not specified - you need to provide the following values in the filter:
|
Parent company | This field is used for selecting parent company in company card. Parent company can have many child companies but only one parent can be set for company. Parent-child relations may be ussed for set issue security, see more |
Child companies | This field is used for selecting child companies in company card. You can enter new value here - in that case a new company will be created in the company directory. |
Dictionary | Field to store some value from specified CRM custom dictionary (only one value). It's possible to add new values to the dictionaries through the fields of this type. The dictionary should be specified in the attribute property "Dictionary". |
Multi Dictionary Values | Field to store several values from specified CRM custom dictionary . The dictionary should be specified in the attribute property "Dictionary". |
Table list | Places a table into Company / Contact card from Table Lists sub-menu. |
Related Projects | You could link some companies and contacts with any JIRA project. See more: Related Projects |
JIRA user | Type to store one or more JIRA users, for example account manager of a company. It's possible to give additional CRM permisions for JIRA users, stored in fields of this type. See more there: Setting up Access to Objects |
JIRA group | Type to store one or more JIRA groups.It's possible to give additional CRM permisions for JIRA users, stored in fields of this type. See more there: Setting up Access to Objects |
Transactions | List of transactions related to the company. You can select fields to show in Company card and in Issue transaction view. |
Counter | Field to set the order number to Company records. There is no possibility to assign number manually, it is made automatically. For every new record Counter field type adds 1 to previous created even if it was deleted. |
Textarea | For multiple string type attributes. Maximum length is 400 symbols (including space and enter). |
Status date | Field to store date of Transaction's status changing. |
Creator | Field to store record creator name (fills in automatically, not editable). |
Creation date | Field to store record creation date (fills in automatically, not editable). |
Updator | Field to store record updator name (fills in and updates automatically). |
Updated date | Field to store record update date (fills in and updates automatically). |
E-mail is valid | Checkbox to show if contact's e-mail passed through validation during Direct Mail process. |
No subscribe me | Checkbox to show if contact had unsubscribed from Direct Mail. |
Epic | Field to store Epic name in Transactions if transaction is in issue which is part of an Epic. |
...