Unique ID's in Medini

medini_1057145546

[External Sender] Hello Support team, We have this observation: Unique ID's across requirements in a project: Working with requirements is Medini synced with codebeamer trackers, the requirement ID's are generated in Medini whenever a new requirement is created (Ex:SR001).  The created ID's are not unique (meaning a requirement is deleted or sub requirement is introduced and renumbering regenerates the ID's with appended values) across the project (the renumbering only happens for a specific tracker requirements and not for the project meaning there could be more than one requirement with the same id).  Is it possible to generate unique ID's (possibility to configure the prefix) in the ID fields for the requirements across a project? Please assist. Thanks! Mit freundlichen Grüßen/ Best Regards/ हार्दिक शुभकामनाओं सहित Kritika Waman ALM Administrator kritika.waman@veoneer.com Direct: + +49 89 262035 518 Mobile: +49 15161696160 Veoneer Konrad Zuse Str. 1, 85716 Unterschleissheim www.veoneer.com     This e-mail is from: Veoneer Germany GmbH Konrad-Zuse-Strasse 1, 85716 Unterschleissheim, Germany Registered Seat: München, Germany Registered under HRB 234759 (district court München) Managing Directors: Thomas Hellerforth, Andreas Deimel, Amelie Maria Petersdotter Heiner Wendels *************************************************************** To read the Company's Information and Confidentiality Notice, follow this link: https://www.veoneer.com/en/important-information-and-confidentiality-notice ***************************************************************

medini_1028038066

Dear Kritika, thank you for your request. The topic with the IDs is indeed not an easy one, since every user has its own counter (the clients are initally disconnected).  1. Präfixes can be given in the Project Preferences (right mouse click on the project and choose Project Settings...) 2. This setting should be part of the Veoneer Template, so that every new project get the same schema. 3. The projects needs to be shared in SVN or GIT to make the IDs visible to everyone. 4. If due to the merge same IDs came in, there is the option to renumber requirement ids: 5. Again after this a notification of the team should be triggered over SVN or GIT.  At this point I have the following suggestion to you:  First: I share this explanation into the Veoneer Forum, so that open points and discussion becomes visible (done here in this forum topic). Second: I modify this ticket as a feature request to enable Central Server Location managing the medini ID to avoid duplicates, since this is not possible with the current rich client set-up (feature request handed over as  #11916 ticket. Thank you again and looking forward to your reply,  Krassi Sincerely Krasimira Kulekova ANSYS medini analyze Support Team medini analyze 2021 R2.1 released - check the Release Notes!