Sync stories between AD2.0 and Enterprise Agile Planning (EAP)

Pelayo
Tera Expert

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:

 

https://docs.servicenow.com/bundle/xanadu-it-business-management/page/product/spw-eap/reference/sync...

 

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

1 ACCEPTED SOLUTION

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!

View solution in original post

6 REPLIES 6

phil_bool_unifi
Tera Guru

That's really interesting to hear.  I was under the impression the same backlog of stories would appear in EAP so long as your Enterprise Agile Teams were aligned, but I haven't got round to testing this yet.  Can I ask how you've confirmed this isn't the case?

Scott Townsend1
ServiceNow Employee
ServiceNow Employee

Hi Pelayo,

 

We use the same table for stories in both EAP and Agile Dev.  However, we use EAP Teams which have a one-to-one mapping.  For the integration, we'll need to map the teams (requiring a change to the integration).  Would you like to get together to discuss?  My email is william.townsend@servicenow.com

 

Thanks,

Scott

 

Hi Scott

 

Thank you for your reply.

 

We found a cleaner way to do this, although we haven't tested it yet.

 

We found out that EAP Teams have a 1:1 mapping with Enterprise Agile Configurations too. This way, once the user creates a story from AD2.0 with an assignment group, we can search for the related EAP Team (since that mapping is also 1:1) and instead of setting that EAP Team, we can set the Enterprise Agile Configuration for the story.

 

This way the OOB integration between AD2.0 and EAP will trigger, since the story has an active EAP Config, and if the EAP Config is set to "Enable agile integration" then the OOB Business rule "Sync assignment group and eap team" will trigger, setting the appropiate EAP Team and being linked from now on on every Assignment Group or EAP Team change.

 

We were confused as to why this was not done by the plugin itself and has to be done by the customer, since it seems to be a reasonable functionality.

 

Kind regards!

fabi0caballer0
Tera Contributor

Pelayo, thank you for sharing these findings. Would you be so kind as to share the result of the test? In my opinion, this functionality should not be configured by the client, it should be OOTB.