What is the best practice for frequently updating process templates?
![]()
Currently I have a Master project with 23 Children that get updated through process sharing so that piece is already in place but I come to the forum to seek others opinions.
I own the process template updates and have weighed pros and cons to different methods but still find myself without a perfect solution.
Here is an example of the unique DB UUID key I am speaking of:
Attribute Customization Validator Script -->, I do mean _r3CWEEtpEeeGtepOyoaYJA as in
<validatorid="com.ibm.team.workitem.valueproviders.VALIDATOR._r3CWEEtpEeeGtepOyoaYJA"name="Vali"providerId="com.ibm.team.workitem.shared.common.internal.valueProviders.ScriptAttributeValueProvider"> <scriptclass="com.example.Validator"path="/workitem/scripts/common/vali.js"/> </validator> Scenario C: Create all my projects on PROD but name them such like ( {name-d}, {name-u}, {name-p}, d for dev, u for uat and p for prod ) - This is awesome because I can copy and paste the full XML from project to project, fetch the JS from attribute customizations and I am done - Downside, anything I create in “d” appears in JRS as if it were in PROD today. We can communicate changes each release but you know the curious ones will “discover” the (new, but unexplained) and want to play. Is there no ideal solution that is fast, easy and able to conceal half-baked changes till fully baked.
The floor is open... :)
|
Accepted answer
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.