|
|
|
|
Introduction
This is the wish list for ClearCase
Here is an overview of the wish list:
Content
Use the following template to specify you wishes. Please remember that there may be thousands of users out there, each with their own wishes. So try to limit yourself to the things that are worthwhile submitting a official RFE (Request For Enhancement) for. More over, please do submit an RFE for it and fill in the RFE number that you get back. Also, add a link to a threat at the discussion forum so that we can update the wish based on the reactions.
More forgiving, intelligent cleartool arguments
| RFE |
unknown |
| Business value to customer |
Low |
| Implementation |
Simple |
| Description |
More forgiving, intelligent cleartool arguments
Sometimes you need a -tag switch when specifying a view tag, other times you don't. If I specify a -tag and I don't need one, why doesn't it just work anyway.
Example: catcs and startview
catcs my_view [error]
startview -tag my_view [error]
I think it would be better if it was able to do the right thing anyway. |
| Rationale |
It would be a bit more consistent |
| Discussion thread |
|
| Posted by |
 jamiedodger at Jul 05, 2007 12:59 |
Google-able error messages
| RFE |
|
| Business value to customer |
Medium |
| Implementation |
Simple |
| Description |
Standard google-able error messages, a bit like Oracle
In Oracle you get a numbered error message before a short description, something like this: ORA-1234
If the short description doesn't make sense, you can look up the error code, and get a lengthier description of the problem, either in the manual, or on the web. Why don't we have a similar thing in CCase
|
| Rationale |
Might help people find answers to their problems |
| Discussion thread |
|
| Posted by |
jamiedodger at Jul 05, 2007 13:04 |
Check out hard-linked elements
| RFE |
|
| Business value to customer |
Medium |
| Implementation |
Needs some kind of redesign |
| Description |
Elements with multiple hard links, when checked out in dynamic views, the checkout appears against only one of those names, whichever you checked out, and the others are seen as "checkedout, but removed". It would be in some ways better if the checked out version appeared against all of these visible pathnames of the element. |
| Rationale |
This more closely models how multiple hard links works in the OS filesystem, and is probably the "right thing to do" |
| Discussion thread |
|
| Posted by |
jamiedodger at Jul 05, 2007 13:08 |
Atomic checkout
| RFE |
|
| Business value to customer |
Medium |
| Implementation |
Medium |
| Description |
Atomic checkout operation, to include copying the data to your view
Sometimes you get a "checkedout, but removed" if you have permission to check out an element but not copy data to your view. Most of the time the user would rather have the checkout fail than be left with a checkedout, but removed, which makes sense to clearcase but not to the user's way of thinking about the world.
|
| Rationale |
It just stops people being confused when this happens. |
| Discussion thread |
|
| Posted by |
jamiedodger at Jul 05, 2007 13:14 |
Predefined "must have" triggers
| RFE |
|
| Business value to customer |
Medium |
| Implementation |
Reasonably easy |
| Description |
Fold standard trigger types into the product - the most frequently implemented trigger types should not be trigger scripts, but brought into the product for 1) speed and 2) so that customers don't have to do standard things themselves
Example: out of the box rmelem should be disabled for most users, and enablable for everyone with a tick box or cleartool chvob type operation
Evil twins should be prevented by default, and allowable with a switch to mkelem, for example. |
| Rationale |
It just seems that the product would be better if every customer didn't have to go through the same process for functionality that could and should be built in |
| Discussion thread |
|
| Posted by |
jamiedodger at Jul 05, 2007 14:18 |
Re-introduce Cleardetails
| RFE |
|
| Business value to customer |
Medium |
| Implementation |
Reasonably easy |
| Description |
Bring back cleardetails
And/Or make clearexplorer faster |
| Rationale |
cleardetails was fast and lightweight |
| Discussion thread |
|
| Posted by |
jamiedodger at Jul 05, 2007 14:26 |
Standard alias for cleartool
| RFE |
|
| Business value to customer |
Low |
| Implementation |
Easy |
| Description |
Make ct a standard alias for cleartool |
| Rationale |
This is a very common thing to do, but we can't rely on it being in place on a client, so if it was a standard thing as part of the product we could all use it. |
| Discussion thread |
|
| Posted by |
jamiedodger at Jul 05, 2007 15:00 |
Transparent ClearCase shell
| RFE |
|
| Business value to customer |
Medium |
| Implementation |
Tricky |
| Description |
A transparent ClearCase shell, that traps writes and transparently checks out files as required in the style of ccfd "ClearCase for Dummies" and also optionally checksin and mkelems as required
|
| Rationale |
This makes writing scripts to work under clearcase easier, because you can treat the filesystem as writeable and not worry about having to checkout files and so on. |
| Discussion thread |
|
| Posted by |
jamiedodger at Jul 05, 2007 15:45 |
Plug-in for Windows Explorer for extra columns
| RFE |
|
| Business value to customer |
Medium |
| Implementation |
Medium |
| Description |
A plugin for Windows Explorer to provide extra columns with ClearCase details e.g. version, type of object, checked out status etc, and a right click menu of options from within Windows Explorer windows. |
| Rationale |
Just so that people using Windows Explorer can see more than just OS-level files and folders with no understanding of the ClearCase nature of those things. |
| Discussion thread |
|
| Posted by |
jamiedodger at Jul 05, 2007 17:31 |
Copy types to other VOB
| RFE |
|
| Business value to customer |
Low |
| Implementation |
Simple |
| Description |
A cleartool command to copy types from one vob to another, such as cleartool cptype trtype:foo@/vobs/A trtype:foo@/vobs/B |
| Rationale |
It would come in handy where you are not using admin vob hierarchy and you don't want to maintain scripts to make types. Any tools for managing types would be handy. |
| Discussion thread |
|
| Posted by |
jamiedodger at Jul 06, 2007 15:13 |
See also
|
|
|
