Using Traditional Scheduler on non-formal projects no longer supported/advised?
Ron De Jong (78●8●5)
| asked Jun 19 '13, 6:04 a.m.
JAZZ DEVELOPER retagged Jun 19 '13, 2:41 p.m. by Amy Laird (165●1●4)
In the past (RTC 3) it was possible, and specifically mentioned, that the Traditional Scheduler could be added to a non-formal based process later:
http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0/index.jsp?topic=/com.ibm.team.platform.doc/topics/t_customize_template_formal_features.html But with version 4, the number of features that can be adopted, has decreased, and the Traditional Scheduler is no longer mentioned: http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/index.jsp?topic=%2Fcom.ibm.jazz.platform.doc%2Ftopics%2Fc_formal_template_customization.html Personally I was never in favor of doing this anyway (just make sure you pick the right basis;-), but I have a couple of projects still requesting this. Can I conclude that this is no longer advisable, or supported? Thanks Ron |
Accepted answer
Hello Ron,
There were too many issues with adapting formal template features to non formal projects. Therefore we no longer support it. You might try contacting IBM consultants to try doing it but still not sure if they are able to do that. Best regards, Krzysztof Kazmierczyk Ron De Jong selected this answer as the correct 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.