The pages Settings in Testersuite and Settings in JIRA show how to set up a link between Testersuite and JIRA per Testersuite environment. On this page we go into more specific detail about how this works in practice. Still have questions? Then contact us at support@testersuite.nl.
Integration Users
When an issue is updated in JIRA and a webhook to Testersuite is set up, in Testersuite the corresponding requirement or defect will be updated by the set integration user.
You can set up a separate integration user in each environment, or deploy the same integration user in multiple environments. For this the integration user in question must be a participant of the appropriate environment(s). This is of course configurable in the administrator portal.
JIRA users in different environments
For each Testersuite environment where the JIRA link is set up, you need the credentials of a JIRA user. This can be the same JIRA user for each Testersuite environment, but you can also choose a different JIRA user for each Testersuite environment who performs the Testersuite updates on the JIRA side.
Permissions and restrictions regarding JIRA projects
If you have set up the JIRA connection for multiple environments, you may not want the same JIRA projects to be used within those different Testersuite environments. The solution to this then is to connect to a different JIRA user for each Testersuite environment. Within the user management in JIRA you then indicate for the relevant user(s) to which projects they have access. Testersuite then respects these rights.
Using the same JIRA projects within different Testersuite environments
If you connect multiple Testersuite environments to the same JIRA site, you can connect Test cycles in different environments to the same Jira project. This makes it possible to retrieve the same user stories as requirements within different Testersuite environments. Using the mapping in Testersuite, these requirements are always kept up to date with the latest information from the JIRA user story. For example:
- In Testersuite environment 1, JIRA user story JRA-123 is retrieved
- This becomes requirement REQ1 in Testersuite environment 1
- In Testersuite environment 2, JIRA user story JRA-123 is also retrieved
- This becomes requirement REQ1 in Testersuite environment 2
- In Testersuite environment 1, requirement REQ1 is updated
- In JIRA, this leads to an update of user story JRA-123
- This in turn leads to an update of REQ1 in Testersuite environment 2
- In JIRA, this leads to an update of user story JRA-123