It's all about the answers!

Ask a question

RTC - Naming Conventions


Sumitra Awasthi (31122) | asked Dec 28 '12, 7:20 a.m.
edited Jun 16 '16, 2:25 a.m. by Ralph Schoon (63.1k33646)

Hi,

Is there any plan to include best practices for RTC Naming Conventions and providing a mechanism  to define naming conventions and enforcing them?

  1. Team Area
  2. Streams
  3. Components
  4. Repository Workspace
  5. Timelines
  6. Iterations
  7. Baselines
  8. Snapshots
  9. Releases
  10. Plans
  11. Project Area
  12. Build Definition
  13. Build Engine
  14. Build Queue

Thanks,

Sumitra

Accepted answer


permanent link
Ralph Schoon (63.1k33646) | answered Dec 28 '12, 11:22 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Dec 28 '12, 11:26 a.m.
Hi Sumitra,

as far as I can tell, there is no way that is out of the box to enforce naming conventions on any of those items. There are probably work items for a few of them and you can request that functionality in an enhancement request with support or here.  It might be possible to come up with automation for some of the elements above, e.g. using Java API custom tools that create the data following the rules and preventing arbitrary users to change/save the data.
Ralph Schoon selected this answer as the correct answer

One other answer



permanent link
Deepali Deshmukh (8913759) | answered Jun 16 '16, 2:24 a.m.
I am looking for the similar functionality, Is this feature included in the latest version of RTC ?

Comments
Ralph Schoon commented Jun 16 '16, 2:27 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

No, there are small additions e.g. to avoid duplicate names. Initial names for workspaces, but that is it.

Your answer


Register or to post 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.