- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2024 08:25 AM - edited 10-23-2024 08:27 AM
With the newly added plugin Enterprise Agile Planning we're able to create stories there and then see them on our Agile Boards, following the docs in here:
However, and after a dive into some of the logic behind it, stories created from Agile Development2.0 are not synced with EAP. Is there any plan to make this a possibility?
If not, we were thinking about a way to make it possible following this logic:
- When a user creates a story in AD2.0, set the EAP team (which makes it available in EAP) with the Story's assignment group.
This approach make stories visible in EAP, but we leave the story without its appropiate eap_config (for us it's impossible to determine what its eap_config should be when creating them from AD2.0) and we suspect it may conflict with some of the syncing logic already implemented.
What are some of your thoughts about this?
Kind regards,
Pelayo
Solved! Go to Solution.
- Labels:
-
Agile Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2024 09:10 AM - edited 10-28-2024 09:16 AM
Hi Fabio,
Yes. In the end, we decided to implement it this way:
- Once a story is created from AD2.0 with an assignment group, we search for its related EAP Team and if found, set the EAP Config for the story. The EAP Config has to be created with the check "Enable agile integration" for the integration to work.
- This triggers the OOB BR "Sync assignment group and eap team" in charge of syncing Agile Stories with EAP and sets the EAP Team.
- For existing stories, we created a fix script very similar to the logic above, but we set the Team AND the EAP Config, because existing stories won't trigger the OOB BR (assignment group changing is a condition of this BR).
In this process we also found a bug in the plugin code, that we are discussing with the ServiceNow Team. There's a script include that does validations on the story team changes that doesn't validate these changes quite right, but it shouldn't be a big issue and we think it will be fixed in future releases of the plugin.
I'll mark this as the solution, thanks for your inquiry!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2024 09:10 AM - edited 10-28-2024 09:16 AM
Hi Fabio,
Yes. In the end, we decided to implement it this way:
- Once a story is created from AD2.0 with an assignment group, we search for its related EAP Team and if found, set the EAP Config for the story. The EAP Config has to be created with the check "Enable agile integration" for the integration to work.
- This triggers the OOB BR "Sync assignment group and eap team" in charge of syncing Agile Stories with EAP and sets the EAP Team.
- For existing stories, we created a fix script very similar to the logic above, but we set the Team AND the EAP Config, because existing stories won't trigger the OOB BR (assignment group changing is a condition of this BR).
In this process we also found a bug in the plugin code, that we are discussing with the ServiceNow Team. There's a script include that does validations on the story team changes that doesn't validate these changes quite right, but it shouldn't be a big issue and we think it will be fixed in future releases of the plugin.
I'll mark this as the solution, thanks for your inquiry!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2024 10:51 AM
Hi Pelayo,
Thanks for sharing your experiences! Help us a lot!
