It seems to me that this would be a simple addition and would be very helpful in correcting a simple spelling error, etc.
As I can find out, this functionality is not available.
Assuming you're talking about the "Check In Comments", this is possible at a highly-administrative level by modifying the database. (And pretty simple, in all honesty.) I think it should stay that way. We don't want iteration comments freely open for edit, in my opinion. The current workaround is sufficient enough as far as I'm concerned.
For example, WTParts:
drop table wtpart_bak;
create table wtpart_bak as (select * from wtpart);
set noteiterationinfo = 'modified check-in comment'
where ida2a2 = (
select w.ida2a2 from wtpart w, wtpartmaster wm
Before & After pictures below.
Not all of us Business Admins have access to the database. And I'm sure even less know much about editing a database or even feel comfortable editing it.
Although you think it's "pretty simple" it's not. Even if I did have access to the database there is no way what-so-ever I would edit the companies database.
This is a good idea. One that should definitely be ACL or Profile controlled to make sure its not open to everyone, but the idea of being able to edit or update incorrect or missing checkin comments is great. This is a highly overlooked capability, but something very beneficial when looking at an object's history. I would definitely support it.
In addition to check-in comments, I would categorize Change management comments as well. Check in comments you could (although annoying, cumbersome, and usually not worth it) back up offline, delete that iteration, import back in and then check it in again with the comment you want. On the other hand, Change Management approval comments seem to have no *simple* recourse to editing.
Although it is good to know the workaround that Ben Perry referred to, however Steve Galayda mentions a significant roadblock that would make a simple user edit (with note and/or history), or admin override, much more user friendly then editing the database.
Ben's workaround is great, but having the right interface to fo that as admin would be really great. I hope it will be implemented in the comming realeases.
The concept is good and like Scott said it should be control by ACL rules so not everyone can edit the comment fields.
For a small company where 1 person wears many hats when it comes to Windchill, Ben Perry's SQL script will provide the needed change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.