Atlassian Jira Cloud connector

Learn how to configure the Atlassian Jira Cloud Connector to synchronize your Jira tickets, users, groups and permissions

+ More

Atlassian Jira Cloud connector

One of the Native Connectors available is Atlassian Jira Cloud connector, which is meant to be used when integrating Matrix42 Pro/IGA to Atlassian Jira Cloud instance. Event-based Jira connector task is used when writing data from Matrix42 Pro/IGA platform towards Jira. Schedule-based Jira connector task is used when reading mass amount of data from Jira Cloud platform towards Matrix42 Pro/IGA. Solution administrators are able configure connection to target Jira Cloud using the Native Connectors admin UI. Processes can be run event-based triggered by Visual Workflow Automation.

Atlassian Jira Cloud connector requires configuration according to customers use case, and in principle configuration has three (3) steps:

Configure connector - enables connector to establish connection to the customers Atlassian Jira Cloud
Configure scheduled task - is used when data is read from the customers Atlassian Jira Cloud
Configure event task - is used when data is written to the customers Atlassian Jira Cloud
1. Also workflow orchestration nodes are required to be configured

Common use cases are:

Create Jira issues based on incident from ESM platform to Jira
Import Jira issues from Jira to ESM platform
Transfer comments between ESM platform and Jira
Transfer resolution between ESM platform and Jira
Create and delete Jira users
Create and delete Jira groups
Add and remove users from Jira groups

General functionalities

Connectors - general functionalities

In this article are described general functionalities for managing native connectors in solution. All Native Connectors are managed from the same connector management UI.

Notice that there are separate descriptions for each connector, where connector specific functionalities and configuration instructions are described in detailed level.

To be able to access connector management, user needs to have admin level permissions to customers Platform configuration. When accesses are granted correctly, connector tab will be visible and user can manage connectors.

Left menu

Connector management is divided into four tabs:

Overview - for creating and updating Native Connectors. The Admin User can see their status, type and how many scheduled or event tasks are associated with them.
Authentication - for creating and updating authentication tasks. Provisioning task for authentication is needed for Secure Access to be able to define which Customers end-users can access to Matrix42 Core, Pro and IGA login page.
Logs - for downloading Native Connector and Secure Access logs from UI.
Settings - general settings for Native Connectors and Secure Access, including environment type for logging and monitoring.

Connectors overview tab

From overview page, user can easily and quickly see status for all connectors.

Top bar:

Status for Native Connectors (EPE)
- Green text indicates that Native Connectors is online. All the needed services are up and running.
- Red text indicates that there is a problem with Native Connectors, all the services are not running.
Status for Secure Access (ESA)
- Green text indicates that Secure Access is online. All the needed services are up and running.
- Red text indicates that there is a problem with Secure Access, all the services are not running.
Native Connectors version number is displayed in top right corner

Top bar for list view:

New connector - opens new window for adding and configuring new connector
Remove connector(s) - workflow references are calculated and pop-up window appears to confirm removal (notice that calculating references can take several seconds)
Export - Admin can export one or more connectors (and tasks) from the environment. Usually used for exporting connectors and connectors (and tasks) from test to prod. Native connectors secret information is password protected.
Import - Admin can import one or more connectors (and tasks) to the environment. Usually used for importing connectors (and tasks) from test to prod.
- Admin cannot import from old EPE UI (Older than 2024.1) to the new one. Source and target environments must have same version.
- Import will fail if the configuration (templates, attributes) is not the same - for example when some attribute is missing
- If you are importing something with the same connector details, it will be merged under existing connector
Refresh - Admin can refresh connectors view by clicking the button.

List view for overview,

Select connector(s) - Select one connector by clicking check box in front of the connector row or clicking check box in the header row will select all connectors
Id - Automatically generated unique ID of the connector. Cannot be edited or changed.
Status - indicates scheduled task status
- Green check mark - Task is executed without any errors
- Red cross -Task is executed, but there have been error
- Grey clock - Task is not executed yet, waiting for scheduling
- Orange - one of the tasks has a problem
- No value - Scheduled based-task is missing
Name - Connector name added to connector settings. Unique name of the connector holding configuration for one data source
Type - indicates target / source system
Scheduled - informs how many scheduled tasks are configured
Event - informs how many event tasks are configured
Manage
- Pen icon - opens connector settings (double-clicking the connector row, also opens settings)
- Paper icon - copies the connector
- Stop - workflow references are calculated and pop-up window appears to confirm removal
Search - User can search connector by entering the search term in the corresponding field . Id, Status, Name, Type, Scheduled and Event fields can be searched.

Scheduled task information (click arrow front of the connector)

When clicking arrow at the beginning of the connector row, all related scheduled and event tasks are shown

Top bar for scheduled tasks

New task - opens configuration page for new task
Remove task(s) - removes the selected task(s) from the system and they cannot be recovered anymore.
Refresh - refresh scheduled-based tasks view
Search - user can search task by entering the search term in the corresponding field for Id, name, enabled, extract/load status.

List view for scheduled tasks

Select task(s) - Select task to be deleted from the list view by ticking.
Id - Unique ID of the task. Generated automatically and cannot be changed.
Name - Task name added to task settings, unique name of the task.
Enabled - Displays is the task scheduled or not
- Green check mark - Task is scheduled
- Red cross - Task is not scheduled
Extract status - Displays status of data extraction from the target directory/system
- Green check mark - data is extracted successfully
- Red cross - data is extracted with error(s) or extraction is failed
- Clock - Task is waiting execution
Load status - Displays status of data export from json-file to customers solution
- Green check mark - data is imported successfully to customers solution
- Red cross - data is imported with error(s) or import is failed
Manage
- Pen icon - opens task settings in own window (double-clicking the task row also opens task settings)
- Paper icon - copies the task
- Clock icon - opens task history view
- Stop - remove task, pop-up window opens to confirm the removal

Scheduled task history view

By clicking the clock icon in the scheduled task row, history for scheduling will be shown.

Top bar for view history

Refresh - refreshes scheduled task status. This doesn't affect task, this only updates UI to show latest information of task run.

List view for scheduled task history

Color of the row is indicating status
- Green - task executed successfully
- Red - error happened during execution
Execution ID - unique ID for the scheduled task row
Extract planned time - when next extract from the directory/application is scheduled to happen
Extract complete time - when extract was completed
Extract status - status for fetching data from the directory/application
Load start time - when next load to customers solution is scheduled to happen
Load complete time - when load was completed
Load status - status for loading information to customers solution

List view for scheduled task status

Actual start time - timestamp for actual start
Users file - JSON file containing user information read from the directory/application
Group file - JSON file containing group information read from the directory/application
Generic file - JSON file containing generic information read from the directory/application
Extract info - detailed information about reading information from the directory/application
Load info - detailed information about loading the information to customers Matrix42 Core, Pro and IGA solution

Edit window for scheduled task

Configuration for scheduled task can be opened by clicking pen icon or double-clicking the task row.

Left menu and attributes varies according to selected options and therefore more detailed instructions for editing tasks can be found from the connector description, but there are common functionalities for all scheduled tasks which are described below.

Saving the task

In case mandatory information is missing from the task, hoovering mouse on top of the save button will show which attributes are still empty.

Top bar for edit scheduled task

Run task manually - admin can run task manually out side of the defined scheduling
Stop task - admin can stop scheduled-based task which is currently running. Task will be stopped and status is changed to be stopped. It waits in this state until the next timing occurs.
Clear data cache - Data cache for the next provisioning of Users and Groups will be cleared. It means that next run is run as first time run.
- By default, we clear the cache everyday at 00:00 UTC
- If you want to clear the cache at different time, then it has to specify some different value in host file 'custom.properties'.
- EPE Cache is also cleared when EPE is restarted, whole environment is restarted, EPE mappings have been changed

Event task information

When clicking arrow at the beginning of the connector row, all related scheduled and event tasks are shown

Top bar for event tasks

New task - opens configuration page for new event task
Remove task(s) - removes selected task(s), pop-up window appears to confirm the removal
Refresh - refreshes event tasks view
Show workflow references - calculates task related workflow relations and statuses. This is very useful if you don't know from which workflows event-based tasks are used.

List view for event tasks

Select task(s) - Select task to be deleted from the list view by ticking.
Id - Unique ID of the task. Generated automatically and cannot be changed.
Name - Task name added to task settings, unique name of the task.
Workflow relations
- Question mark shows pop-up window with detailed information about the reference
Workflow status
- Not used - No relations to workflow
- In use - Workflow(s) attached to task, task cannot be removed
Manage
- Pen icon - opens task settings in own window
- Paper icon - copies the task
- Stop icon - removes the task, pop-up window appears to confirm the removal

Edit window for event task

Configuration for event task can be opened by clicking pen icon or double-clicking the task row.

Edit event task window

Task usage, editable? - this appears when editing existing task and changing the task usage type will break workflows
Mappings type, editable? - this appears when editing existing task and changing the mappings type will break workflows

Saving the task

In case mandatory information is missing from the task, hovering mouse on top of the save button will show which attributes are still empty.

Authentication tab

Authentication for Matrix42 Core, Pro and IGA solutions are configured from authentication tab, notice that only some of the connectors (directory connectors) are supporting authentication, so its not possible to create authentication tasks to all available connectors.

Top bar for authentication

New connector - opens new window for configuring new connector (notice that not all connectors are supporting authentication)
Remove connector(s) - removes selected task(s), pop-up window appears to confirm the removal
Export - user can export one or more tasks from the environment. Usually used for exporting tasks from test to prod. EPE connectors are password protected.
- Note that Realm for authentication tasks is not exported, you need to set that manually after importing
Import - user can import one or more tasks to the environment. Usually used for importing task from test to prod.
Refresh - refreshes authentication tasks view

List view for authentication overview

Select connector(s) - Select one connector by clicking check box in front of the connector row or clicking check box in the header row will select all connectors
Id - Automatically generated Unique ID of the connector. Cannot be edited or changed.
Name - Connector name added to connector settings. Unique name of the connector holding configuration for one data source
Type - indicates target / source system
Count - informs how many authentication tasks are configured
Manage
- Pen icon - opens authentication task setting in own window
- Paper icon - copies the task
- Stop icon - removes selected task

Authentication task information

When clicking arrow at the beginning of the connector row, all related scheduled and event tasks are shown

Top bar for authentication overview

Create new task - opens configuration page for new authentication task
Remove task(s) - removes selected task(s), pop-up window appears to confirm the removal
Refresh - refreshes authentication tasks view

List view for authentication overview,

Select task(s) - Select task to be deleted from the list view by ticking.
Id - Unique ID of the task. Generated automatically and cannot be changed.
Name - Task name added to task settings, unique name of the task.
Manage
- Pen icon- opens task settings in own window (double-clicking the task row, also opens settings window)
- Paper icon - copies the task
- Stop icon - removes the task, pop-up window appears to confirm the removal

Logs tab

Logs tab is for downloading Native Connector and Secure Access logs from UI for detailed troubleshooting.

epe-master logs - contains warning, debug and error level messages about Native Connectors and info how long task actions has been taken.
epe-worker-ad logs - contains extract data status of Active Directory connector (what Native Connector is loading to to customers Matrix42 Core, Pro and IGA solution). If selection is empty, it means that directory is not in use in this environment.
epe-worker-azure logs - contains extract data status of Entra ID (what Native Connector is loading to to customers Matrix42 Core, Pro and IGA solution). If selection is empty, it means that directory is not in use in this environment.
epe-worker-ldap logs - contains extract data status of LDAP (what Native Connector is loading to to customers Matrix42 Core, Pro and IGA solution). If selection is empty, it means that directory is not in use in this environment.
epe-launcher logs - contains information about EPE launches
datapump-itsm logs - Contains information about data export to customers Matrix42 Core, Pro and IGA solution.
esa logs - Contains information about Secure Access authentication.

Settings tab

Settings tabs is used for monitoring environments with connectors.

Environment type - is mandatory to be in selected and information is used for example defining alert critically.
- Test - select this when your environment is used as testing environment
- Prod - select this when your environment is used as production environment
- Demo - select this when your environment is used as demo or training environment
- Dev - select this when your environment is used as development environment

What we are monitoring?

Failures in scheduled based provisioning (extracting data, exporting data to ESM, outdated certificates, incorrect passwords, incorrect search base/filter, incorrect mappings, etc.)
Failures in event based provisioning (fail to write to AD/Azure, etc.)
Event-based provisioning - which connectors are used for writing data towards applications/directories.
ESA more than ten failed login attempts to one user in past 3 days
Environment type - is mandatory to be in selected and information is used for example defining alert critically.

Data migrations

Do not click “Migrate attribute mappings” or “Migrate workflows”, if not requested to do so by Matrix42.

General guidance for scheduled tasks

How to Create New Scheduled Task to import data

For configuring scheduled-based provisioning task, you will need access to Administration / Connectors tab.

1. Open the Administration area (a cogwheel symbol).

2. Open Connectors view.

3. Choose Connector for Scheduled-based task and select New Task
Note! If connector is not created, you have to choose first New connector and after that New task.

4. Continue with connector specific instructions: Native Connectors

Should I use Incremental, Full or Both?

Scheduled task can be either Incremental or Full -type.

Do not import permissions with AD and LDAP incremental task

Incremental task has issue with permissions importing. At the moment it is recommended not to import group memberships with incremental scheduled task.

On Microsoft Active Directory and OpenLDAP connectors, remove this mapping on incremental task:

Setting on Scheduled tasks:

Incremental type is supported only for Microsoft Active Directory, LDAP and Microsoft Graph API (formerly known as Entra ID) Connectors.

Incremental type means, that Native Connectors (EPE) fetches data from source system, using changed timestamp information, so it fetches only data which is changed or added after previous incremental task run.

When Incremental type task is run for very first time, it does a full fetch (and it marks the current timestamp to EPE database), thereafter, task uses that timestamp to ask the data source for data that changed since that timestamp (and then EPE updates the timestamp to EPE database for next task run). Clearing task cache doesn't affect this timestamp, so Incremental task is always incremental after first run.

Full type is supported for all Connectors.

Full type import fetches always all data (it's configured to fetch) from source system, on every run.

Both Full and Incremental type tasks use also Task cache in EPE, which makes certain imports faster and lighter for M42 system.

By default that task cache is cleared ad midnight UTC time. When cache is cleared, next import after that is run without caching used to reason if data fetched should be pushed to ESM, all fetched data is pushed to ESM. But after that, next task runs until next time cache is cleared, are using EPE cache to determine if fetched data needs to be pushed to ESM or not.

You can configure at what time of day task cache is emptied, by changing global setting in EPE datapump configuration:

/opt/epe/datapump-itsm/config/custom.properties

which is by default set to: clearCacheHours24HourFormat=0

You can also clear cache many times a day, but that needs to be thinked carefully, as it has impact on overall performance as EPE will push changes to ESM, that probably are already there, example(do not add spaces to attribute value): clearCacheHours24HourFormat=6,12

After changing this value, reboot EPE datapump container to take change into use.

Recommendations:

Have always by default Full type scheduled task.

If you want to fetch changes to data fetched already by full task, more frequently than you can run full task, add also incremental task. Usually incremental task is not needed.

Recommended Scheduling Sequence

Recommended scheduling sequence, depends how much data is read from Customers system/directory to the Matrix42 Core, Pro or IGA solution and is import Incremental or Full.

Examples for scheduling,

Total amount of users	Total amount of groups	Full load sequence	Incremental load sequence
< 500	< 1000	Every 30 minutes if partial load is not used Four (4) times a day if partial load is used	Every 10 minutes
< 2000	< 2000	Every 60 minutes, if partial load is not used Four (4) times a day if partial load is used	Every 15 minutes
< 5000	< 3000	Every four (4) hours, if partial load is not used Twice a day if partial load is used	Every 15 minutes
< 10 000	< 5000	Maximum imports twice a day, no matter if partial load is or is not used	Every 30 minutes
< 50 000	< 7000	Maximum import once a day, no matter if partial load is or is not used	Every 60 minutes
Over 50 000	Over 7000	There might be a need for another EPE-worker, please contact Product Owner	Separately evaluated

Please note that if there are several tasks running at the same time you may need more EPE-workers. The tasks should be scheduled at different times and can be completed according to the table above. However, if there are more than 6 tasks running at the same time, the number of epeworkers should be increased. It's best practice not to schedule tasks to run at same time, if possible.

Recommendations related to performance
If the amount fo data to be imported is over 10000 concider these things:
Adjust log level of ESM and DATAPUMP to ERROR-level, to lowe the amount of logging during task run
Have as few as possible automations starting immediately for imported datacards (listeners, handlers, workflows), as those make ESM to take longer time handling new datacards.

Set removed accounts and entitlements status removed/disabled

With this functionality, you can mark account and entitlement status to e.g. Deleted or Disabled, when account or entitlement is removed from source system. Starting from version 2025.3 you can also set status to generic objects (not only to accounts/identities and entitlements/groups).

For version 2025.3 and newer

In version 2025.3 these settings are moved from properties files to Task UI. Also you can now set these settings for Generic objects, which have not been possible before this version.

There is separate configuration for each scheduled task, and for all mapping types. Here is example of this config on task:

For version 2025.2 and older

This functionality is available for “full” type scheduled tasks.

Settings are on datapump dockers configuration file. To change those parameter values, you need to set those in /opt/epe/datapump-itsm/config/custom.properties file.

Configuration

To enable disabling functionality, datapump config should have these parameters set to true:

disable.unknown.esm.users=true
disable.unknown.esm.groups=true

Those 2 parameters are false by default in 2024.2 and 2025.1 versions. In 2025.2 and newer version those are true by default.

Next are these parameters:

personTemplateStatusCodeAttributeKey=accountStatus
personTemplateStatusAttributeDisabledValueKey=Deleted
groupTemplateStatusCodeAttributeKey=status
groupTemplateStatusAttributeDisabledValueKey=5 - Removed

First two attributes should point to the DatacardHiddenState attribute in the User template, and tell which value should be send there when the user is deleted.

By default its accountStatus and Value 5 - Removed on IGA Account template.

All these needs to match with the attribute configuration:

Same thing applies for the next two paramaters, but its for Groups.'

If you need to change those parameters in properties file, do changes in Datapump container to file: /opt/epe/datapump-itsm/config/custom.properties and those changes will then survive over container reboot and will be copied on reboot to /opt/epe/datapump-itsm/config/application.properties.

Description

Tasks save their __taskid__ shown as Task Id mapping in the UI to the datacards, its then used to determine if the datacard was added by this task. In case there are multiple tasks with different sets of users.

This field was previously used as datasourceid, but since we moved to the model where connector can have multiple tasks its identifier cannot be used anymore, thats why the field was repurposed as taskid instead.

Taking users as an example, when task runs ESM is asked for the list of users that have its taskid in Task Id mapping field, and doesn't have a personTemplateStatusAttributeDisabledValueKey value in the personTemplateStatusCodeAttributeKey

This result is then compared to what the task fetched, and the datacards of users that were not fetched have their personTemplateStatusattribute set to value specified in the config - 5 - Removedby default.

Example log below shows described process and informs that one user was removed.

Same thing applies to groups but groupTemplateStatusattributes are used instead.

Notes

Feature works only with full fetch scheduled tasks..
No support for generic templates yet, only identity and access
When migrating from the previous versions where datasourceid was still used it needs to run at least once to set its taskid’s in the datacards first.
EPE identifies Disabled users or groups as the ones that were removed from the AD, at the present we do not support statuses related to the entity beign active or not.
EPE does not enable users back on its own.
If more than one tasks fetches the same users or groups it may overwrite the taskid in the datacard depending on which task ran last. It is suggested that many full type tasks are not fetching same user or group.
Always do configuration file changes to custom.properties, do not change only application.properties as those changes are lost on container reboot if you have not done same changes to custom.properties.

Configure Jira Cloud connector

How to create new Jira connector

For configuring provisioning , you will need access to Matrix42 Pro/IGA Platform configuration console.

1. Open the Administration area (a gear symbol).
2. Open Connectors view.
3. Choose New connector

4. Select Data Source type Atlassian Jira Cloud

5. Fulfill information related to Jira solution

Connector name - give your connector a friendly name (name can be changed afterwards). Jira connector host url should be in format: https://instancename.atlassian.net
Host URL - host address which will be used connecting to Efecte solution
User name - user who created Access token (Jira Service Accounts are not supported)
Access token - Access tokens are valid max for one year (Jira side limitation), so remember to document when token will expire, so you remember to create new token and configure it to Jira Connection before it expires. For more information see:https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/
- Access token value is Jira users API token value
WebAPI user - Efecte solution WebAPI user name
- List of all Efecte local users
WebAPI password - Efecte solutions WebAPI users password

6. Save connector information.

7. After saving the connector details, open connector again and click test connection button to see if connector can connect to target Efecte solution.

8. When connection is successful, you can continue to creating Scheduled task and/or Event-based task

Step-by-Step Instructions to create Scheduled task

Atlassian Jira Cloud connector is used for to read user, group and ticket information from Jira and it is configured from Matrix42 Pro/IGA platform by creating scheduled-based connector task.

How to create new scheduled-based task

For configuring scheduled-based connector task, you will need access to Efecte Platform configuration console. Note! If connector is not created, you have to create first “new connector” and after that you are able to create new tasks.

1. Open the Matrix42 Pro/IGA Platform configuration view (a gear symbol).
2. Open Connectors view.
3. Choose Connector for scheduled-based task and select + new task

4. Define scheduling for the task (if and how scheduled task should be run periodically). Choose scheduling sequence, which depends how much data is being read from Jira.

5. Fill in task details

Fill in unique task name for the scheduled-based task, notice that name cannot be changed afterwards.
Task usage indicated that is the task used for reading data or writing data. Note that If event type is changed afterwards it can break the workflows.
Mappings type depends what type of information is read from the directory
- Identity and access rights - is used when Jira users and group information are read from the application
- Single (identity only) - is used when only Jira user information is read from customers Jira
- Single (access right only) - is used when only Jira group information is read from customers Jira
- Generic (one template) - are used when other Jira items are read from customers Jira, like for example stories, tickets, bugs, etc.
Jira query - It is best practice to test your Jira query (JQL) in actual Jira system, before using it in task configuration.
See also Jira documentation:
https://support.atlassian.com/jira-service-management-cloud/docs/use-advanced-search-with-jira-query-language-jql/
https://www.atlassian.com/software/jira/guides/jql/cheat-sheet#key-jql-functions

6. Fill in failure information. Optional settings for failure handling, if scheduled task fails it can create data card to Matrix42 Pro/IGA solution that displays the error. If failure settings are defined , the administrator does not need to manually check the status of scheduled tasks.

Failure template - Select a template of datacard which will be created in case of any errors during data reads (connection to data sources,timeouts,etc.)
Failure folder - Select folder where failure data card is stored.
Failure attribute - Select an attribute where in the failure template should the error information be stored in.

7. Fill in mappings

It is mandatory to set target template & -folder, datasourceid and unique id values which are used for identifying data between customers Jira and Efecte solution.

Target template - Select a template to define attribute mappings
Select a template to define attribute mappings
Target folder - Select a folder from a list of folders. The list is narrowed down to match compatibility with selected Template.

Data Source Type mapping - optional. If it is set, it writes connectors type to that attribute.
Task Id mapping - Task id number is written to this attribute. Correct attribute to choose depends on how your Template is configured.
Set value to datacard fo object deleted from source system - This functionality is activated by setting checkbox on. When some object that was previously read from Jira to Matrix42 Pro/IGA solution is deleted from Jira. This scheduled task notices that is was deleted and marks that datacard selected attribute with value you want. This can be for example used to set Status attribute to Deleted. This Attribute name and Attribute value needs to be set based on how your Template is configured.
Attribute mappings
1. External attribute - which attribute from the Jira is read
2. Local attribute - to which attribute in Matrix42 Pro and IGA attribute is mapped to
Add attributes to attribute mappings, by choosing New attribute

8. Save task from the Save button. If some required attributes are missing the save button is displayed as grey and it will display what is missing from the settings.

9. You have now configured schedule based connector task to read data from Jira to your solution

You can now wait until task is started based on scheduling or
Run task manually - by clicking the button task is configured to be scheduled to start immediately. Usually for test runs or if you don't want to change the schedule settings, but want to run the task now.

10. If task is executed manually ("Run task" clicked) or it is run according to scheduling, task status can be reviewed by View history:

Step-by-Step Instructions to create Event-based task

1.Open the Matrix42 Pro/IGA Administration area (a cogwheel symbol) in right upper corner.

2. Open Connectors view

3. Choose Atlassian Jira Cloud Connector from the Overview and Event-based tasks and button + New Task

4. Fill in unique name for the provisioning task

Mapping type needs to be Generic Template when handling (for example tickets) other object types than users and groups.

5. Fill in attribute mapping section.

Note! The content is different depending on what you have selected as the value in the field Mappings type.

Target Template - Template which contains data you want to send to Jira (or fetch from Jira)

Target Folder - Folder which contains data you want to send to Jira (or fetch from Jira)

It is possible to set additional attributes by choosing “New Attribute” and then writing attribute name, and accept it by clicking “Add item ”. This is very useful if you have added your own custom attributes to Jira.

It is possible to define which attribute information is written to the Jira.
There can be several provisioning task for different purpose towards Jira.
To add Jira ticket, you must set at least issueType, project and summary, depending on your Jira configuration maybe also other attributes. Confirm needed attributes from Jira system.

7. Save provisioning task from the Save button

8. The next step is to configure the workflow to use this event-based task. From workflow engine in Matrix42 Pro/IGA Service Management platform, it is possible to execute provisioning activities towards Jira. This means that any of the available Activity's can be run at any point of the workflow using “Orchestration” node.

Example of Orhcestration node settings for Jira:

Configure bi-directional connector

When configuring bi-directional connector it requires that workflow's orchestration nodes and both scheduled- and event-based tasks are configured to Matrix42 Pro/IGA solution. In this chapter are scenario examples how to configure bi-directional connector between Matrix42 Pro/IGA solution and Jira Cloud.

Scenario 1.

Matrix42 Pro/IGA creates ticket to customers Jira based on ticket type and Jira sends ticket back based on status.

Create Generic Event-based task to Matrix42 Pro/IGA for creating tickets, for example here is event-based task that is using ticket template
Create workflow to Ticket template in Matrix42 Pro/IGA which defines the rules for when a ticket goes to Jira, for example here is workflow that sends ticket to Jira when status is New and type is Incident and support group is Software team
After that, in order to get the status back to Matrix42 Pro/IGA you need a scheduled task that reads the jira requests status back to Matrix42 Pro/IGA. For example, here scheduled task that is reading Jira issues that have project “Efecte tickets” and status is Completed

Scenario 2.

Matrix42 Pro/IGA creates ticket to customers Jira and updates existing ticket in Jira with changed information (description field has been updated).

Create Generic Event-based task to Matrix42 Pro/IGA for creating tickets, for example here is event-based task that is using ticket template
Create workflow to Ticket template in Matrix42 Pro/IGA which defines the rules for when a ticket goes to Jira, for example here is workflow that sends ticket to Jira when status is New and type is Incident and support group is Software team
After that, in order to get the description back to Matrix42 Pro/IGA you need a scheduled task that reads the jira requests description back to Matrix42 Pro/IGA. For example, here scheduled task that is reading Jira issues that have project “Efecte tickets” and status is not Completed

Scenario 3.

Matrix42 Pro/IGA creates manual access right request as a ticket to Jira, based on status change it is send back to Matrix42 Pro/IGA.

Create Generic Event-based task to Matrix42 Pro/IGA for creating tickets, for example here is event-based task that is using IGA Administration task template
Create workflow to IGA Administration task template in Matrix42 Pro/IGA which defines the rules for when a task goes to Jira, for example here is workflow that sends task to Jira when status is Open and task category is Manual access
After that, in order to get the status back to Matrix42 Pro/IGA you need a scheduled task that reads the jira requests status back to Matrix42 Pro/IGA. For example, here scheduled task that is reading Jira issues that have project “Efecte tickets” and status is Completed

Workflow activities

The Efecte Provisioning Engine (EPE) provides the possibilities to orchestrate the following activities to Jira.

Add User to Group

In the illustration above, the Person attribute configuration should point to the template where the orchestration node finds the user’s data (usually IGA account). The Role attribute needs to be configured to define where the orchestration node finds the available roles (directory groups where the user should be removed). There might be single or multiple attribute groups configured in a “Role attribute”. The list of available registered directory Tasks is fetched from the EPE-master.

Exception handling:

The result of a node will be in the “Completed” state only in the case when all user’s group memberships will be updated successfully. In the case when, for example, the user will be successfully removed from 5 out of 6 groups then the result of a node will be in the “Exception” state.
Hence the mapping for distinguishedName JSON field, for both Identity and Access Right is required. If mapping won’t be found then the orchestration node will result in an “Exception” state.
The attempt to remove a user from a group which they do not belong will end as a failure.
The attempt to add a user to a group to which he already belongs will end as a failure.
Details about successfully/unsuccessful updated user’s group membership can be found in logs.
Provisioning and group membership exceptions are optional properties on this workflow node. Admins can configure this properties in use where exceptions can be written if any exceptions exists during the provisioning actions.

Create user

The creating new user orchestration node read attributes from Data Cards in question and execute API call to Jira. Created Entity Id should be filled with attribute that contains accountID value of the new user.

There are two ways to create the password for a new user for their first login.

Define “Default” password in the Provisioning Task -configuration view
- That password will only be used by users, when they login into the system for the first time
Generating random password in the workflow and select into which attribute on Identity Mapping data-card it was written to
Possibility to choose if the password must change at the first login or not. Administrators can make the selection for this directly from the workflow User Creation orchestration node.
There are different ways to provide password for the first login for the end-user. Depending on customers needs it is possible to use workflow functionalities to send the password directly to the end user via email or sms. Another option is to send the password for first login to the manager, who will provide it for the end-user. EPE’s Orchestration node itself DO NOT provide that functionality, it needs to be defined elsewhere.

Provisioning exception is an optional property on this workflow node. Admins can configure this property in use where exceptions can be written if any exceptions exists during the provisioning actions.

Create Group

Admins choose the correct Jira “Target” and are able to view the configuration. The creating new group orchestration node read attributes from Data Cards in question and executes API call to Jira.

Created Entity Id attribute is mapped to attribute in Efecte that contains groupID value of the new group.

Delete Group

Admins choose the correct Jira “Target” and are able to view the configuration. Deleting group orchestration node read attributes from Data Cards in question and executes API call to Jira.

Role group attribute must be mapped to attribute in Efecte that contains groupID value of the group that is going to be deleted.

Delete User

Admins choose the correct Jira “Target” and are able to view the configuration. Deleting user orchestration node read attributes from Data Cards in question and executes API call to Jira.

Person attribute* must be mapped to attribute in Efecte that contains AccountId value of the user that is going to be deleted.

Remove User from Group

In the illustration above administrators can choose the correct Jira “Target”.

Person attribute* must be mapped to attribute in Efecte that contains AccountId value of the user that is going to be removed from group

Role attribute* must be mapped to attribute in Efecte that contains groupID value of the group that is going to be removed from the user.

Create Jira Ticket

In the illustration above administrators can choose the correct Jira “Target”. Target is selectable for those epetask that are containing at least attributes datasourceid, issuetype, project and summary. for example

Known restrictions

Reading comments from Atlassian Jira Cloud to Matrix42 Pro or IGA solution

If you try to read comments directly to comments attribute to Matrix42 Pro or IGA datacard, comments will be duplicated on every scheduled task run.

Instead of reading those comments directly to comments attribute, you need to use helper temp attribute where you map Jira comment. And update actual comments based on that temp attribute value, if actual comments attribute doesn't yet contain that comment. This can be done with Matrix42 core and pro platform customisation tools. Contact Matrix42 consultants to get more detailed information how this can be done.

Troubleshooting

In this chapter are described troubleshooting options,

In case failure template is used, check correct data card
Check scheduled task history from connector management
Check Efecte Provisioning Engine logs

connector cloud integration jira atlassian jira cloud native connector

Table of Contents

Contact Us

Atlassian Jira Cloud connector

Contact Us

Service Management

Identity Governance and Administration (IGA)

Platform

Release Notes for M42 Professional, IGA, Conversational AI

Other Material

Services

Atlassian Jira Cloud connector

Learn how to configure the Atlassian Jira Cloud Connector to synchronize your Jira tickets, users, groups and permissions

Atlassian Jira Cloud connector

General functionalities

General functionalities

General guidance for scheduled tasks

General guidance for scheduled tasks

How to Create New Scheduled Task to import data

For configuring scheduled-based provisioning task, you will need access to Administration / Connectors tab.

Should I use Incremental, Full or Both?

Do not import permissions with AD and LDAP incremental task

Recommendations:

Recommended Scheduling Sequence

Recommended scheduling sequence, depends how much data is read from Customers system/directory to the Matrix42 Core, Pro or IGA solution and is import Incremental or Full.

Set removed accounts and entitlements status removed/disabled

For version 2025.3 and newer

For version 2025.2 and older

Configuration

Description

Notes

Configure Jira Cloud connector

How to create new Jira connector

Step-by-Step Instructions to create Scheduled task

How to create new scheduled-based task

Step-by-Step Instructions to create Event-based task

Configure bi-directional connector

Workflow activities

Add User to Group

Create user

Create Group

Delete Group

Delete User

Remove User from Group

Create Jira Ticket

Known restrictions

Reading comments from Atlassian Jira Cloud to Matrix42 Pro or IGA solution

Troubleshooting

Related Articles