Hi Sarthak,

I would make sure to base projects on a common process template that has all the required attributes in the future. You could even use the process that is defined in one project area by other project areas. The downside of this is that there is only very limited support for process customization in the project areas that inherit the process. If you do, you will loose the ability to see changes in the project that you base upon.

It is also possible to create the attributes by the plugins. Please find an example code snippet below. What I am not sure of is, if it is possible to configure the attributes that are created in the UI e.g. to add the attribute presentations to the UI. I have no code and I am not sure if it is possible to create the attribute presentations. It should be possible- the client does it in the UI - but the code could be internal in the SDK.

            IWorkItemClient workItemClient= (IWorkItemClient) fTeamRepository.getClientLibrary(IWorkItemClient.class);

            IAttribute customString = workItemClient.findAttribute(fProjectArea,
                    fCustomStringAttributeID, null);

            if(null==customString&&fCreateAttributesIfMissing){
                customString=workItemClient.createNewAttribute(fProjectArea,fCustomStringAttributeID,AttributeTypes.SMALL_STRING,IAttribute.FULL_TEXT_KIND_DEFAULT, monitor);
                customString.setDisplayName("Created String ("+fCustomStringAttributeID+")");
                customString=workItemClient.saveAttribute(customString, monitor);
            }
           
            if(null!=customString){
                if(!workItem.hasCustomAttribute(customString)&&fCreateAttributesIfMissing){
                    // If not defined in the process template it has to be manually created
                    workItem.addCustomAttribute(customString);
                }
                if(workItem.hasCustomAttribute(customString))
                    workItem.setValue(customString, fCustomString);
            }