bin/otobo.Console Admin::Service::Import is missing Description with installed ServiceCatalog

[StefanAbel-OTOBO]

When you try to import a Service via otobo.Console.pl it is missing a Description, as soon as the ServiceCatalog package is installed.
There is no option for it.

otobo@0f3c0ebf6a1f:~$ bin/otobo.Console.pl Admin::Service::Add --name 'Applications' --parent-name '' --criticality '3 normal' --type 'Other'
Adding a new service...
ERROR: OTOBO-otobo.Console.pl-Admin::Service::Add-46 Perl: 5.38.5 OS: linux Time: Thu Sep  4 14:15:40 2025

 Message: Need Descriptions!

 Traceback (185962):
   Module: Kernel::System::Service::ServiceAdd Line: 875
   Module: Kernel::System::Console::Command::Admin::Service::Add::Run Line: 172
   Module: (eval) Line: 488
   Module: Kernel::System::Console::BaseCommand::Execute Line: 482
   Module: Kernel::System::Console::InterfaceConsole::Run Line: 88
   Module: bin/otobo.Console.pl Line: 40

Error: Can't add service.
otobo@0f3c0ebf6a1f:~$ bin/otobo.Console.pl Admin::Service::Add --help

Add new service.

Usage:
 otobo.Console.pl Admin::Service::Add --name ... --criticality ... --type ... [--parent-name ...] [--comment ...]

Options:
 --name ...                     - Name of the new service.
 --criticality ...              - Criticality of the new service.
 --type ...                     - Type of the new service.
 [--parent-name ...]            - Parent service name. If given, the new service will be a subservice of the given parent.
 [--comment ...]                - Comment for the new service.
 [--help|h]                     - Display help for this command.
 [--no-ansi]                    - Do not perform ANSI terminal output coloring.
 [--quiet]                      - Suppress informative output, only retain error messages.

[stefanhaerter]

Confirmed. However, in my opinion, the solution needs to be discussed in the light of interferences with https://github.com/RotherOSS/ImportExportStandardObjects.

[stefanhaerter]

I thought this to be an easy fix, however it is not. The POD states:

ServiceCatalog/Custom/Kernel/System/Service.pm

Lines 825 to 859 in 5a99ad0

	=head2 ServiceAdd()
	add a service
	my $ServiceID = $ServiceObject->ServiceAdd(
	Name => 'Service Name',
	ParentID => 1, # (optional)
	ValidID => 1,
	Comment => 'Comment', # (optional)
	UserID => 1,
	# ---
	# ITSMCore
	# ---
	TypeID => 2,
	Criticality => '3 normal',
	# ---
	# Rother OSS / ServiceCatalog
	Descriptions => {
	en => {
	DescriptionShort => 'Service A',
	DescriptionLong => 'This is Service A.',
	ContentType => 'text/html',
	},
	de => {
	DescriptionShort => 'Service A',
	DescriptionLong => 'Das ist Service A.',
	ContentType => 'text/html',
	},
	},
	TicketTypeIDs => [ 1, 2, 3 ],
	Keywords => 'service hints for filter',
	# EO ServiceCatalog
	);
	=cut

I think it needs to be discussed how much of that complexity we can and should impose on the user.