Maintenance is complete- We've moved from the domain to click to read more
As part of our journey to complete our separation work and our future integration with Micro Focus, we've now updated our domain for the community. This is an interim step, which will be followed by a series of future update / improvements: - Piloting Idea boards - Refreshing the entire UI. (more to come later) - and more
Agile Manager: Enhancement Requests

Request Single Integration ID

Trusted Contributor.

Request Single Integration ID

As a user, I would like to have a single ID for assets across AGM and ALM.  It is difficult to keep track of two IDs and it doesn't make sense we have two separate IDs across two HP products.


Super Contributor.

Re: Request Single Integration ID

ALM and Agile Manager are two different systems that can be integrated for all or for some of the items. This integration can be modified according to the user needs. Having said that, both product can not predict the user needs and manage their IDs accordingly.


We know that even though the entity ID is purely a unique identification of the entity, it is massively used when communication over entity is done, and that the fact that the same (logical) entity has different identifications in ALM and in Agile Manager is confusing.

We propose solving it by having a user defined field that in Agile Manager will hold the ALM ID and vice versa. This way the ID from both tools is searchable in both tools, and the relevant entity can be found given an ID no matter what its origin is.


Thank you,


Trusted Contributor.

Re: Request Single Integration ID


Thank you for responding.  When demoing the *solution* to my SDLC core team the number one issue that came up was that we have 2 HP software programs that are sold as a solution but they do not share a unique ID.  The enhancement request would make this a tighter integration, and a more clean solution as a whole.  I understand there are challenges, but it might be worthwhile to research the task and add value to the solution.

We currently do what you propose as a workaround (by having UDFs that store each others ID), but think about ALI and how that works.  It ties to the ID of the requirement or defect.  Having a SINGLE ID would allow users to submit code changes and builds in BOTH tools offering an even tighter integration.  Currently the solution only provides ALI to be tied to one or the other (AGM OR ALM, not both). 



Chris Carpenter