Single, shared configuration for many projects

Owned by Łukasz Krupa (Unlicensed)
Last updated: Dec 11, 2020 by Łukasz Krupa (Deactivated)
1 min read

Context

Context is an answer to shared configuration between different:

  • Projects
  • Issue Types


Context configuration options

  • Status - by default configuration is disabled, in order to enable you have to fill all required fields.
  • Project
  • Issue Type - JIRA issue type from chosen project. 
  • Remote Context - Choose corresponding remote context.
  • JQL- filter out issues that will be synchronized (if issue does not meet given condition - they do not belong to this synchronization scope.).



Context Status Consequences

  • If context is disabled in LOCAL JIRA - all events (triggers) will be ignored. No data will recorded into queues.
  • If context is disabled in LOCAL JIRA but enabled in REMOTE - incoming messages will arrive but won't be processed.
  • If context is enabled in LOCAL JIRA but disabled on REMOTE - events will be processed, changes will be recorded in queues and sent to REMOTE; however REMOTE won't process communication any further (no response will arrive until contract will be enabled again in REMOTE).
  • Both disabled in the same time - no communication in those contract scope.