It's all about the answers!

Ask a question

How do I separate out a set of ID numbers for certain work item categories?


A S (58216) | asked Feb 23 '18, 11:01 a.m.

 I have within the RTC section of my CLM installation several work item types - Task, Deployment (an extension of Task), Defect, Story, Epic.  With heavy usage on all sides it has come to the point that Defect 4321 may be implements in Deployment 4231 and this has become confusing.  


How do I separate out ID so that i can get something like -- 

Story :: 10,000 onwards
Defects :: 20,000 onwards 
Deployments :: 40,000 onwards   
Tasks :: 60,000 onwards 
Epics :: 90,000 onwards


Comments
A S commented Feb 23 '18, 11:09 a.m.

 I used to be able to do it in ClearQuest many years ago, unfortunately I don't remember how I did it.  Don't have my notes from that far back. :-(


Donald Nong commented Mar 02 '18, 12:21 a.m.

I don't think you can do this in ClearQuest either. You can allocate an ID block in a ClearQuest MultiSite environment, and the block is for a site, not for a type. You can always create a custom attribute for this purpose if you really want to.


A S commented Mar 06 '18, 3:52 p.m.

I explained this before.  It was a custom field that incremented the number every with a prefix e.g. IN2901 --> IN2902 --> IN2903... every time a new Incident occurred.  While Defects had numbers like DF1234 --> DF1235 --> DF1236...


It was NOT the underlying CQ number.  That was unique for every artifact within CQ.  I don't see a way of doing it within RTC and what I have been seeking help for.


A S commented Mar 06 '18, 3:56 p.m.

I explained this before.  It was a custom field with a prefix that incremented the number every item of that type created  e.g. IN2901 --> IN2902 --> IN2903... every time a new Incident occurred.  While Defects had numbers like DF1234 --> DF1235 --> DF1236...


It was NOT the underlying CQ number.  That was unique for every artifact within CQ.  I don't see a way of doing it within RTC and what I have been seeking help for.


Donald Nong commented Mar 06 '18, 6:58 p.m.

Do you happen to use a hook and within it read a database element such as an Oracle sequence to generate the unique number? If so, you have to develop an RTC extension (using Java) to do something equivalent.


A S commented Mar 07 '18, 1:12 p.m.

Unfortunately it has been about 10 years since I last administered CQ. I don't remember.  

showing 5 of 6 show 1 more comments

Accepted answer


permanent link
Geoffrey Clemm (30.0k23035) | answered Feb 23 '18, 8:17 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

 In RTC this is not supported, and because you can change the type of a work item, doesn't really make sense.   Once you changed the type of a work item, it's ID would no longer be in the "right" range.

Ralph Schoon selected this answer as the correct answer

Comments
A S commented Mar 01 '18, 11:48 a.m.

That is a big headache for people, trying to use the tool as a comprehensive SDLC tool.  The system generated ID should be unique for each item and hidden except to the admin view, but the ID being used as a tracker visible the end-user should be manageable by the admins.


That is why new tools like Service Now are dominating the market.  They have the basics correct, like ClearQuest used to.

Your answer


Register or to post your answer.