Custom settings under JiraSalesforceDetail
Published Date: 05-08-2024
Read Time:
NOTE: For every Jira instance a separate record is created. For Example: If there are two Jira instances integrated via Sinergify, then there will be two records in JiraSalesforceDetail such as J1 and J2. For each record, the configuration setting will be stored as done for the instance.
Name | Field | Value | Created | Description |
---|---|---|---|---|
Jira instance Name (Server or cloud) | DefaultInstance | - | Automatic | Manage from the Admin Settings screen. Do not delete/modify the record directly. Use Admin Settings to perform changes. |
DefaultProject | - | Automatic | Jira Project key of the default project selected in the Project Configuration screen. Do not delete/modify the record directly. Use Admin Settings to perform changes. | |
Display_Name | - | Automatic | Name of the Integration User. Do not delete/modify the record directly. Use Admin Settings to perform changes. | |
Edit_Jira_In_SF | True/False | Automatic | Enable editing of Jira issues in Salesforce. If marked as 'false', then users cannot edit Jira issues from Salesforce. | |
Enable_Feed_Sync | True/False | Automatic | Enable to sync feed posts and attachments. | |
Field Mapping Sync Time | - | Automatic | Save the time to schedule the Jira configuration Sync. | |
File_Size | - | Automatic | Stores the Jira file storage limit. | |
Jira_Comment_As_Private | Private/Public | Automatic | Store your Jira comments with the public or private flag to segment the comments. | |
Jira_Type_Server | True/False | Automatic | Select if your Jira instance is based on cloud or on-premises. | |
JiraCommentQualifier | - | Automatic | Add a qualifier for Jira comments to be synced in Salesforce. For example, if you want only specific Jira comments to sync in Salesforce. Let’s say #SendtoSf will be the qualifier so only comments starting with #SendtoSf will sync in Salesforce. | |
JiraCommentsSyncToJiraIssue | True/False | Automatic | Enable syncing of Jira comments in Salesforce under the Jira comment object. | |
Project Records Per Page | - | Automatic | Show the Number of Projects in Pagination on Project Configuration Tab. | |
Relationship_Type | - | Automatic | Choose how you want to link Jira with a Salesforce record i.e One to One or One to Many. | |
Store_Jira_Comment_in_Case | True/False | Automatic | Store incoming Jira comments as case comments as well. | |
Sync_SF_Attachment | True/False | Automatic | Enable auto-syncing of Salesforce case Attachments/Files to related Jira issue. | |
Sync_SF_Comments | True/False | Automatic | Enable auto-syncing of Salesforce case comments to related Jira issues. | |
SyncJiraAttachmentsToSalesforce | True/False | Automatic | Allow syncing of Jira attachment in Salesforce. | |
Update_Status_From_Salesforce | True/False | Automatic | Enable updating of Jira status from Salesforce. | |
CreateLinks | - | Manual | Create Salesforce records links on Jira. Links are the Salesforce hosted page for showing the record details on Jira without logging into Salesforce. The links are secured with encrypted value and timestamp, which can be defined by Salesforce Admins using TimeStamp record. | |
Reporter_User_Email | email/username | Manual | Define how to find the Jira user related to the current Salesforce user - using user ‘email’ or ‘username’. | |
SalesForceDomain | - | Manual | Salesforce site URL created for Jira. | |
StatusTransition | - | Manual | Add Jira status separated by a comma for which you want to restrict the Status change feature. | |
SyncLegacyJiraComment | True/False | Manual | Enable this for syncing current Jira comments in Salesforce on linking. | |
TimeStamp | - | Manual | Provide a valid time for Salesforce Detail Link responsible for showing Salesforce details from Jira. | |
AllJiraProjectsSearch | True/False | Manual | Search for Jira issues under all projects using the Search Jira feature. |
A separate unique record will be created for JiraLegacy_Filter in the JiraSalesforce_Detail custom setting:
Name | InstanceNumber | Value Field | Created | Description |
---|---|---|---|---|
JiraLegacy_Filter | 1 | - | Manual | After enabling 'Reporting' for the Jira field to update the legacy data for the newly enabled field, users have to schedule the job ’ScheduleBatchToAutoUpdateJira’. To add the filter to the records, use this custom record. For example, Samantha does not want to update the Close Jira records so she can pass the value as Where Status='Close'. |
A separate unique record will be created for JiraErrorLogs_Duration in the JiraSalesforce_Detail custom setting:
Name | InstanceNumber | Value Field | Created | Description |
---|---|---|---|---|
JiraErrorLogs_Duration | 2 | Add number of days | Manual | Delete the logs older than the specified number of days. |
A separate unique record will be created for GuestUserID in the JiraSalesforce_Detail custom setting:
Name | InstanceNumber | Value Field | Created | Description |
---|---|---|---|---|
GuestUserID | 0 | 18 digit Guest user Id | Manual | Add 18 digit Guest user id. |
Custom Settings in Sinergify Triggers
Name | Record Name | Active | Object | |
---|---|---|---|---|
Sinergify Trigger | AddJiraComments | True | JiraIssueComments__c | Mark Active as True or False to turn the trigger ON or OFF respectively. |
AddJiraCommentsfromIdea | True | IdeaComment | ||
FeedItemTrigger | True | FeedItem | ||
JiraAutoAttachment | True | Attachment | ||
JiraAutoComment | True | CaseComment | ||
JiraAutoFileAttach | True | ContentDocumentLink | ||
JiraIssueTrigger | True | JiraIssueTrigger | ||
JiraRelationshipTrigger | True | JiraRelationshipTrigger | ||
UpdateFieldWithData | True | UpdateFieldWithData |