As part of an ActiveControl <> JIRA integration, a Tester has to be assigned to the Business Task being automatically created.

ActiveControl integrations traditionally rely on the username on the ITSM system matching that of the SAP username. Based on this, a user field in the ITSM ticket is then assigned as the Default Tester on the Business Task.

This is typically not the case in JIRA – because user accounts in JIRA are email addresses. To mitigate this issue as part of our out-of-the-box JIRA integration, a user exit solution that was built for a customer in 2017 is now part of standard ActiveControl (since AC8.20). These user exits attempt a user mapping based on email address stored against the user in JIRA and in SAP. If these match, then the Tester can be assigned based on the User assignment on the JIRA ticket.


Configuration

1. Add standard user exit /BTI/TE_EXIT_WSCREATESTER_0080 into /BTI/TE_EXITC table in the Domain Controller.

2. Add standard user exit /BTI/TE_EXIT_WSCHNGTESTER_0082 into /BTI/TE_EXITC table in the Domain Controller.


Other information

(1) Please refer to these Knowledge Articles on Basis Technologies’ Support Portal for further information and possible configuration setup:

(i) Assign testers at System/System Role level within the Integration Framework Link
(ii) Integrating across to the Business Task Owner field with the Integration Framework Link 1 Link 2

(2) Please note that reference to HEADER-CF_550 as part of the configuration does not require the configuration of a custom field within the ActiveControl UI. This custom field is a ‘hidden’ field utilised solely by the Integration Framework.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment