Risk of Changing Process Configuration Source RTC 3.0
One answer
Comments
There was an issue with a custom attribute in our project area and the only solution is to change its attribute id. The reason was it has a duplicate ID with a default attribute. This bug was generated on our RTC 2.0 and was migrated to RTC 3.0
Yes, if you are fixing a problem like that, then that sounds like your best (and perhaps only) approach. The system should prevent you from saving an attribute definition if the id of that attribute is already in use. Is this something you can recreate? If so, it would be good to document how it happened, and file it as a bug.
1 vote
Yes it was documented and we filed it as a bug and what I have mentioned above is the fix. However they have not answered what is the worst case that can happen if we implement this. A backup of project area process template can rollback the changes right?