Creation Rules with multiple Integrations
Right now, I have 2 active Integrations that write to 2 different defect folders (different field mappings) within my project. For each integration, I have created a creation rule based on Jira project names. I am guessing I may not have this set up correctly. From within a test run, if I create a defect, select the Jira project (from a pick list) and submit, it creates the defect in the folder defined in the 1st integration (see below) and it is not shared with Jira. Does anyone have any suggestions or is this a bug?
1st Integration:
Creation Rule for 1st Integration
1st integration Field Mapping:
2ndIntegration:
Creation Rule for 2nd Integration:
2nd Integration Filed Mapping:
David Allison
Eargo
------------------------------
Comments
-
Debbie Mitchell Jama Staff, Data Exchange, Jama Connect Interchange™ (JCI), Product Manager Moderator Posts: 39Hi Dave, thanks for reaching out. When you create a defect from a test run in Jama, which set in Jama does the defect land in?
------------------------------
There is a setting in Admin > Project > Settings tab called "Save Test Run Defects here". My first hunch is that these defects are getting sent to a set in Jama that your integration is not looking at.
Debbie Mitchell
Product Manager
Jama Software
------------------------------
-------------------------------------------
Original Message:
Sent: 10-03-2023 08:46
From: David Allison
Subject: Creation Rules with multiple IntegrationsRight now, I have 2 active Integrations that write to 2 different defect folders (different field mappings) within my project. For each integration, I have created a creation rule based on Jira project names. I am guessing I may not have this set up correctly. From within a test run, if I create a defect, select the Jira project (from a pick list) and submit, it creates the defect in the folder defined in the 1st integration (see below) and it is not shared with Jira. Does anyone have any suggestions or is this a bug?
1st Integration:
Creation Rule for 1st Integration
1st integration Field Mapping:
2ndIntegration:
Creation Rule for 2nd Integration:
2nd Integration Filed Mapping:
------------------------------
David Allison
Eargo
------------------------------
0 -
That is probably it. That would lead to 2 other questions:
- If I have JCI setup the way I do, will it ever work for defects created for a test run that use the second integration? I am guessing this is causing a problem as the defect is created in vv-set-11 Firmware Defects (from above), but the mapping is for VV-SET-12 Software Defects (also, from above example) and JCI isn't acting on them. Though it also appears JCI is not acting on the ones that are placed in VV-SET-11 when Jira Project TNP is selected.
- Is there any way to accomplish what I am trying to do (separate the bugs for clarity) and use different mappings depending on Jira project. I know if I manually create a defect in VV-SET-12 that it is managed properly by JCI
David Allison
Eargo
------------------------------
-------------------------------------------
Original Message:
Sent: 10-05-2023 07:01
From: Debbie Mitchell
Subject: Creation Rules with multiple IntegrationsHi Dave, thanks for reaching out. When you create a defect from a test run in Jama, which set in Jama does the defect land in?
------------------------------
There is a setting in Admin > Project > Settings tab called "Save Test Run Defects here". My first hunch is that these defects are getting sent to a set in Jama that your integration is not looking at.
Debbie Mitchell
Product Manager
Jama Software
------------------------------
Original Message:
Sent: 10-03-2023 08:46
From: David Allison
Subject: Creation Rules with multiple IntegrationsRight now, I have 2 active Integrations that write to 2 different defect folders (different field mappings) within my project. For each integration, I have created a creation rule based on Jira project names. I am guessing I may not have this set up correctly. From within a test run, if I create a defect, select the Jira project (from a pick list) and submit, it creates the defect in the folder defined in the 1st integration (see below) and it is not shared with Jira. Does anyone have any suggestions or is this a bug?
1st Integration:
Creation Rule for 1st Integration
1st integration Field Mapping:
2ndIntegration:
Creation Rule for 2nd Integration:
2nd Integration Filed Mapping:
------------------------------
David Allison
Eargo
------------------------------
0 -
Debbie Mitchell Jama Staff, Data Exchange, Jama Connect Interchange™ (JCI), Product Manager Moderator Posts: 39
Hi Dave,
1. Since all your test runs defects are automatically being created in a single set in Jama (the one specified in Admin > Project > Settings), a JCI integration is only going to pick up those defects and send them to Jira if it is looking at that set. So if you have a second integration looking at a different set, you're right that it will not be picking up test run defects unless a user moves them there manually.2. You can still automatically redirect your test run defects to different Jira projects using your existing setup, with the following adjustments -
-
- Make sure the field mapping groups in both integrations are pointing to your Jama test run defects set (configured in Admin > Project > Settings > "Save Test Run Defects here").
- Leave the Creation Rules set up as they are in the images above.
- In each new defect created from a test run, ensure the appropriate Jira Project is selected. Depending on your business flow, this could be done when the defect is initially created, or some time later.
- Both JCI integrations will continually watch the test run defects set. Whenever an item has a Jira project of LC1 or TNP selected, the item will be synced to the corresponding project in Jira.
If this configuration doesn't work for you, let me know and we can set up a quick call. I also saw you created a support ticket with this question; I'll ask the Support team to go ahead and mark that ticket as resolved so we don't have two threads going.
------------------------------
Debbie Mitchell
Product Manager
Jama Software
------------------------------
-------------------------------------------
Original Message:
Sent: 10-06-2023 06:33
From: David Allison
Subject: Creation Rules with multiple IntegrationsThat is probably it. That would lead to 2 other questions:
- If I have JCI setup the way I do, will it ever work for defects created for a test run that use the second integration? I am guessing this is causing a problem as the defect is created in vv-set-11 Firmware Defects (from above), but the mapping is for VV-SET-12 Software Defects (also, from above example) and JCI isn't acting on them. Though it also appears JCI is not acting on the ones that are placed in VV-SET-11 when Jira Project TNP is selected.
- Is there any way to accomplish what I am trying to do (separate the bugs for clarity) and use different mappings depending on Jira project. I know if I manually create a defect in VV-SET-12 that it is managed properly by JCI
David Allison
Eargo
------------------------------
Original Message:
Sent: 10-05-2023 07:01
From: Debbie Mitchell
Subject: Creation Rules with multiple IntegrationsHi Dave, thanks for reaching out. When you create a defect from a test run in Jama, which set in Jama does the defect land in?
------------------------------
There is a setting in Admin > Project > Settings tab called "Save Test Run Defects here". My first hunch is that these defects are getting sent to a set in Jama that your integration is not looking at.
Debbie Mitchell
Product Manager
Jama Software
Original Message:
Sent: 10-03-2023 08:46
From: David Allison
Subject: Creation Rules with multiple IntegrationsRight now, I have 2 active Integrations that write to 2 different defect folders (different field mappings) within my project. For each integration, I have created a creation rule based on Jira project names. I am guessing I may not have this set up correctly. From within a test run, if I create a defect, select the Jira project (from a pick list) and submit, it creates the defect in the folder defined in the 1st integration (see below) and it is not shared with Jira. Does anyone have any suggestions or is this a bug?
1st Integration:
Creation Rule for 1st Integration
1st integration Field Mapping:
2ndIntegration:
Creation Rule for 2nd Integration:
2nd Integration Filed Mapping:
------------------------------
David Allison
Eargo
------------------------------
0 -
-
Yeah, I was trying to keep them logically separated (FW vs SW), but I don't think I can and get everything to sync. They will have to be separated by filtering I guess. I know there is a way to convert to a new type, but how should I handle moving the defects in vv-set-12 to vv-set-11 as they have a different prefix (vv-bug-### vs vv-swbug-###)?
------------------------------
David Allison
Eargo
------------------------------
-------------------------------------------
Original Message:
Sent: 10-09-2023 08:39
From: Debbie Mitchell
Subject: Creation Rules with multiple IntegrationsHi Dave,
1. Since all your test runs defects are automatically being created in a single set in Jama (the one specified in Admin > Project > Settings), a JCI integration is only going to pick up those defects and send them to Jira if it is looking at that set. So if you have a second integration looking at a different set, you're right that it will not be picking up test run defects unless a user moves them there manually.2. You can still automatically redirect your test run defects to different Jira projects using your existing setup, with the following adjustments -
- Make sure the field mapping groups in both integrations are pointing to your Jama test run defects set (configured in Admin > Project > Settings > "Save Test Run Defects here").
- Leave the Creation Rules set up as they are in the images above.
- In each new defect created from a test run, ensure the appropriate Jira Project is selected. Depending on your business flow, this could be done when the defect is initially created, or some time later.
- Both JCI integrations will continually watch the test run defects set. Whenever an item has a Jira project of LC1 or TNP selected, the item will be synced to the corresponding project in Jira.
If this configuration doesn't work for you, let me know and we can set up a quick call. I also saw you created a support ticket with this question; I'll ask the Support team to go ahead and mark that ticket as resolved so we don't have two threads going.
------------------------------
Debbie Mitchell
Product Manager
Jama Software
------------------------------
Original Message:
Sent: 10-06-2023 06:33
From: David Allison
Subject: Creation Rules with multiple IntegrationsThat is probably it. That would lead to 2 other questions:
- If I have JCI setup the way I do, will it ever work for defects created for a test run that use the second integration? I am guessing this is causing a problem as the defect is created in vv-set-11 Firmware Defects (from above), but the mapping is for VV-SET-12 Software Defects (also, from above example) and JCI isn't acting on them. Though it also appears JCI is not acting on the ones that are placed in VV-SET-11 when Jira Project TNP is selected.
- Is there any way to accomplish what I am trying to do (separate the bugs for clarity) and use different mappings depending on Jira project. I know if I manually create a defect in VV-SET-12 that it is managed properly by JCI
David Allison
Eargo
Original Message:
Sent: 10-05-2023 07:01
From: Debbie Mitchell
Subject: Creation Rules with multiple IntegrationsHi Dave, thanks for reaching out. When you create a defect from a test run in Jama, which set in Jama does the defect land in?
------------------------------
There is a setting in Admin > Project > Settings tab called "Save Test Run Defects here". My first hunch is that these defects are getting sent to a set in Jama that your integration is not looking at.
Debbie Mitchell
Product Manager
Jama Software
Original Message:
Sent: 10-03-2023 08:46
From: David Allison
Subject: Creation Rules with multiple IntegrationsRight now, I have 2 active Integrations that write to 2 different defect folders (different field mappings) within my project. For each integration, I have created a creation rule based on Jira project names. I am guessing I may not have this set up correctly. From within a test run, if I create a defect, select the Jira project (from a pick list) and submit, it creates the defect in the folder defined in the 1st integration (see below) and it is not shared with Jira. Does anyone have any suggestions or is this a bug?
1st Integration:
Creation Rule for 1st Integration
1st integration Field Mapping:
2ndIntegration:
Creation Rule for 2nd Integration:
2nd Integration Filed Mapping:
------------------------------
David Allison
Eargo
------------------------------
0