Use Cases

Jira to Jira

Create Issue

Jira A

  • Configure Account
  • Configure Event Handler

In this example only "Requirement" Issues created in the "PROD" Project will create an event that is passed to the remote system.

Jira B
  • Configure Account
  • Create an Operation Scheme with supported Operation →"CREATE_ISSUE"
    • Edit mapping entries
      • Map project
      • Map issue type
      • Map summary
      • Map a customfield for the remote issue key (this will be needed in further communication)
      • Map additional values of your choice
  • Configure Incoming Events
  • Associate Operation Scheme to Incoming event
  • In this case the incoming event "Jira_8.5.1_ISSUE_CREATE" will call an CREATE_ISSUE action. The fields that will be copied from the remote issue are defined in the mapped Operation Scheme. (ISSUE_CREATE (id:9) in this example)


Update Issue

Jira A
  • Configure Account
  • Configure Handler

Jira B
  • Configure Account
  • Create an Operation Scheme with supported Operation →"UPDATE_ISSUE"
    • Edit mapping entries
      • Map identifier (in this case the remote issue is storing the issue key in customfield_10300)
      • Map additional values of your choice
  • Configure Incoming Events
  • In this case the issue will be identified by the issueKey that is stored in the remote issue in customfield_10300.
  • The Issue Picker field will be filled directly.
  • Applications and Country will be filled according to the mapping that is configured.
  • For Single Value Mapping the value from customfield will be handled as one value.
  • For Multi Value Mapping the value from customfield will be split at ",". After seperating the elements, every entry will be mapped according to the mapping.
  • The mapping supports using the ID. In most cases also the name (eg. IssueType: "Bug") is supported.