Package and Deploy cannot see Management SmartObjects. The Management SmartObjects are available for use within the Designer but when trying to package and deploy - they are missing.
K2 does not allow the Package and Deployment of System SmartObjects (ex. Management SmartObjects) because they have a system binding. This is expected behavior to prevent deploying over the K2 System SmartObjects in the target environment.
Here is a list of the Management SmartObjects:
Event; Group; K2 Application; Library List; List Template; Recycle Bin; Role Site; Site; Template; User.
There is no way to convert the Management SmartObject (SmO) to a 'Packageable' SmartObject; you must remap the controls with a new SmartObject.
The best method is to create a copy of the Management SmartObjects in Designer. This will ensure that you still have all the functionality from the Management SmartObject but the copy will not have a system binding. While in Designer, navigate to the Management SmartObjects and left-click on a SmartObject. You will click on 'Save As' and then you can give it a new name and save it to a different category. Once you have a copy of the SmartObject, you will replace the old SmartObject in the forms and views with the new copy SmartObject. This can be a tedious process but once completed we will be able to Package and Deploy the solution without an issue.