Custom Settings and Usage
Published Date: 01-06-2026
Read Time:
|
S.No |
Custom Setting Name |
Object Name |
Api Name |
Description |
|---|---|---|---|---|
|
|
CallBack URL |
CallBack_URL |
Grz_Sf__CallBack_URL__c |
These custom settings are used to store the callback url generated during authentication. |
|
|
Detail Page Fields |
Detail_Page_Fields |
Grz_Sf__Detail_Page_Fields__c |
This is used to store the record of linked object fields that are displayed during the encrypted links. |
|
|
JIRA Login Settings |
JIRA_Login_Settings |
Grz_Sf__JIRA_Login_Settings__c |
This is used to store the access token details. (Deprecated) |
|
|
JiraErrorCode |
JiraErrorCode |
Grz_Sf__JiraErrorCode__c |
This is used to store the error codes for which resyncing is enabled. |
|
|
JiraSalesforceDetail |
JiraSalesforceDetail |
Grz_Sf__JiraSalesforceDetail__c |
This is used to store the configuration for the overall behavior of Sinergify. |
|
|
Reporting Permissions |
Reporting_Permissions |
Grz_Sf__Reporting_Permissions__c |
It is used to store the ID for which the Jira Field Permission will be enabled for the reporting fields. |
|
|
SFjiraTarget_Triggers |
SFjiraTarget_Triggers |
Grz_Sf__SFjiraTarget_Triggers__c |
This custom setting is used for Jira to SF syncing. |
|
|
Sinergify Action Process |
Sinergify_Action_Processes |
Grz_Sf__Sinergify_Action_Processes__c |
Whenever a user authenticates the Instance, this setting is automatically created. |
|
|
Sinergify Action Resync Schedule |
Sinergify_Action_Resync_Schedule |
Grz_Sf__Sinergify_Action_Resync_Schedule__c |
When you enable the sync error toggle for the first time, this setting is automatically created. |
|
|
Sinergify Trigger |
Sinergify_Trigger |
Grz_Sf__Sinergify_Trigger__c |
It is used to enable or disable the Sinergify package triggers. |
|
11. |
Validation |
Validation |
Grz_Sf__Validation__c |
It stores the validation fields that need to be checked while updating a Jira from Salesforce. (Deprecated) |
|
12. |
Related List |
Related List |
Grz_Sf__RelatedList__c |
For Internal Purposes only. |
|
13. |
Comments And Attachments Tab Settings |
Comments_And_Attachments_Tab_Settings |
Grz_Sf__Comments_And_Attachments_Tab_Settings__c |
This is used to control the tab settings for the Manual comment and attachment button. |
Custom settings under JiraSalesforceDetail
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.
Custom Settings Records under JiraSalesforceDetail
|
Name |
Field |
Value |
Created |
Description |
|---|---|---|---|---|
|
Jira instance Name (Server or cloud)
|
DefaultInstance |
- |
Automatic |
This setting stores if the instance is the default instance or not. |
|
DefaultProject |
- |
Automatic |
The Jira Project key of the default project is selected in the Project Configuration screen. Do not delete/modify the record directly. Use Admin Settings to perform changes. |
|
|
Display_Name |
- |
Automatic |
This setting is used to store the username of Basic Authentication. |
|
|
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. Public Flag: Visible to Community |
|
|
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 the 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 issues. |
|
|
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 attachments 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, Salesforce links, 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 the 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. |
|
|
|
Auto_SF_Comment_Sync_Type |
True/False |
|
This is used to store the type of comment syncing Public, private, or both. |
|
|
Disable_TimeRemaining |
True/False |
|
This is used to disable the remaining time of the time tracking. |
|
|
ErrorTimeInterval |
|
|
This is used for storing the values of the Resync scheduler. |
|
|
Is_Plugin_Enabled |
True/False |
Manual |
For Internal Purpose only. |
|
|
Jira_Comment_As_Private |
True/False |
Manual |
This is used to store whether the comment is public or private. |
|
|
Show_PotentialResults |
True/False |
Manual |
This is used to store the data to show or hide the potential results on the Create screen. |
|
|
SyncErrorAttempts |
- |
- |
This is used to store the number of attempts to resync the error. |
|
|
SyncJiraAttachmentsToSalesforce |
True/False |
|
This is used to store the value of whether we want to sync the Jira attachment to Salesforce. |
|
|
Sync_SF_Comments |
True/False |
Manual |
This is used to store the value whether we want to sync the SF comments. |
|
|
Time Tracking |
|
|
This is used to store the format of the Time Tracking field. |
|
|
AttachmentQualifier |
|
|
This is used to store the qualifier used in the Case attachment. |
|
|
CaseCommentQualifier |
|
|
This is used to store the case comment qualifier. |
|
|
InstanceNumber |
|
Automatic |
This is a unique number to store the instance number. |
|
|
JiraAttachmentQualifier |
|
|
This is used to store the Jira attachment qualifier. |
|
|
|
|
|
|
|
|
Show_JiraHistory_Activity |
True/False |
|
This is used to control the display of the Show Jira history and activity tab. |
|
|
SyncError |
|
|
This is used to store the values to sync the error. |
|
|
Sync_SF_Attachment |
True/False |
|
This is used to store the boolean values to sync SF attachments. |
|
S.No |
Record Name |
Instance Name |
Value field |
Created |
Description |
|---|---|---|---|---|---|
|
1. |
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'. |
|
2. |
JiraErrorLogs_Duration |
2 |
Add the number of days |
Manual |
Delete the logs older than the specified number of days. |
|
3. |
GuestUserID |
0 |
18 digit Guest user ID |
Manual |
Add an 18-digit Guest User ID. (Will be used if you are using webhook and Site) |
|
4. |
CheckCustomSetting Access |
can be any between 9991-9999 |
Yes/No |
- |
To bypass the view all custom setting permission for private custom setting. |
|
5. |
Enable Custom Access |
>100 |
Yes (To enable the Custom Permission)
|
Manual |
This record will handle the permission for the Create and Search button on the related list. |
Custom Settings Records under Detail Page Fields
|
Name |
Field API Name |
Field Label |
Object Name |
Order |
|---|---|---|---|---|
|
1 |
Subject |
Subject |
Case |
1 |
|
2 |
Description |
Description |
Case |
2 |
Custom Settings Records under Sinergify Action Process
|
Name |
Created |
Description |
|---|---|---|
|
Auto Create Jira |
Automatic |
Re-sync the Creation of Jira Issues using automation that may have failed due to any System Failure. |
|
Feed Syncing |
Automatic |
Re-sync the Jira Issues related to specific Salesforce Object's feed which may have failed due to any System Failure. |
|
Sync Attachments from Salesforce |
Automatic |
Re-sync the automated syncing of Attachments on Jira Issues from Salesforce to Jira which may have failed due to any System Failure. |
|
Sync Comments from Salesforce to Jira |
Automatic |
Re-sync the automated syncing of Comments on Jira Issues from Salesforce to Jira which may have failed due to any System Failure. |
|
Update JiraIssue From Salesforce |
Automatic |
Re-sync the automated syncing of Jira Issue details from Salesforce to Jira which may have failed due to any System Failure. |
|
Update JiraIssue From Sobject |
Automatic |
Re-sync the Jira Issues related to specific Salesforce Object on the basis of Jira-Salesforce object field Mapping which may have failed due to any System Failure. |
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 |
||
|
|
CaseToJiraTrigger |
True |
Case |
|
|
|
CustomJiraIssueTrigger |
True |
Jira issue |
|
|
|
FeedCommentTrigger |
True |
Feed comment |
|
|
|
JiraToCaseTrigger
|
True |
Jira issue |
|
Feedback


