Page Comparison

Schema:

• ID
• CONNECTION_ID - specifies connection to which this contract belongs
• CONTRACT_NAME
• CONTRACT_TYPE - depreciated
• PROJECT_TYPE - specifies project type e.g. "software" or "service_desk" (since IssueSYNC v1.6)
• ISSUE_TYPE - id of issue type, which this contract affects
• JQL_CONSTRAINTS - additional JQL constraints provided for contract
• PROJECT_ID
• REMOTE_CONTEXT_NAME - remote contract name
• STATUS - specifies if the contract is enabled or disabled
• ATTACHMENTS - specifies if attachment synchronization has been enabled
• ADD_PREFIX_TO_ATTACHMENTS
• SYNCHRONIZE_ALL_ATTACHMENTS
• COMMENTS - stores information about comments synchronization preferences (on, off, external tab, service desks internal, service desks shared)
• ALL_COMMENT_RESTRICTIONS
• ENABLE_EXTERNAL_COMMENT - specifies if you want to synchronize comments only from IssueSYNCs dedicated tab (depreciated since IssueSYNC v1.6, logic moved to COMMENTS)
• SYNCHRONIZE_ALL_COMMENTS
• FIELD_MAPPING - depreciated
• WORKFLOW_MAPPING - id of workflow mapping provided in IssueSYNC configuration
• WORKLOGS - specifies if you want to synchronize worklogs (only for IssueSYNC server version)

Schema:

• ID
• AUTHOR
• BUILD_IN_COMMENT_ID - id of built-in comment id (if it wasn't created in IssueSYNCs dedicated tab)
• COMMENT - comment body/ user input
• COMMENT_TYPE
• CONTRACT_ID - local contract id
• DATE_INTERNAL - time of original creation in issue (by user)
• DATE_EXTERNAL - time of creation in issue after synchronization (by technical user)
• ISSUE_ID
• REMOTE_COMMENT_ID
• SYNC_ISSUE_ID

Schema:

• ID
• CONNECTION - local connection id
• CONTRACT_NAME - remote contract name
• FIELD_NAME - remote exposed field name/alias
• FIELD_TYPE - type of remote field e.g. text field, textarea, user picker
• UPDATE_DATE

Schema:

• ID
• LOCAL_ATTACHMENT_ID - local attachment id
• REMOTE_ATTACHMENT_ID - remote attachment id (created during synchronization process)
• RESPONSE_MESSAGE
• SYNC_ISSUE - relation to SYNC_ISSUE

Schema:

• ID
• CONNECTION_ID - local connection id related to the massage
• CONTRACT_ID - local contract id related to the massage
• CREATE_DATE
• ISSUE_ID - id of local issue, which was/will be affected by he massage
• ISSUE_KEY - key of issue, which was/will be affected by he massage
• JSON_MSG - core information for IssueSYNC, contains change informations
• MATCH_QUEUE_ID - id of remote QUEUE_OUT
• MSG_TYPE
• STATUS
• UPDATE_DATE - when update has been performed

QueueIn Statuses:

• NEW (0) 
  Message has arrived.
• PROCESSING (1)
  Update after create scenario - waits until response with created issue id will return.
  Message is awaiting some other dependent messages. Status very rare to happen.
• DONE (5)
• ERROR (6)

• RETRY (4) <- This one can be set manually (SQL Update Statement) to force resend of ERROR messages. *

Schema:

• ID
• CONNECTION_ID - local connection id related to the massage
• CONTRACT_ID - local contract id related to the massage
• CREATE_DATE
• ISSUE_ID - id of local issue, which was/will be affected by he massage
• JSON_MSG - core information for IssueSYNC, contains change informations
• MATCH_QUEUE_ID - id of remote QUEUE_IN (until outgoing job runs it will remain empty)
• MSG_TYPE
• STATUS
• UPDATE_DATE
• EVENT_DATE - when event provoked synchronization

QueueOut Statuses:

• NEW (0) 
  Message has arrived.
• SENT (2)
  Message sent to (or pulled by) the remote.
• DONE (5)
• ERROR (6)
• RETRY (4) *

Schema:

• ID
• ISSUE_ID
• ARCHIVED_DATE
• CONNECTION_ID
• CONTRACT_ID
• CREATE_DATE
• JSON_MSG
• MATCH_QUEUE_ID
• MSG_TYPE
• QUEUE_ID
• QUEUE_TYPE
• STATUS
• UPDATE_DATE