Currently, the yc-app-cli only support mapping all event to one EventType. If it is unmappable, the issue is discarded completely. Although users can run a second instance of yc-app-cli to map to other type, this would make double-creating issues in iCalendars produced from both instances.
So the yc-app-cli should support mapping issues to different event types. While many settings like OtherStringMappings can be shared, however, the AlarmSetting must be separated and users need to define them repeatedly (in fact, users can use spring's property placeholder to avoid declaring similar settings again and again)
CXwudi
commented
1 year ago
Currently, the
yc-app-clionly support mapping all event to oneEventType. If it is unmappable, the issue is discarded completely. Although users can run a second instance ofyc-app-clito map to other type, this would make double-creating issues in iCalendars produced from both instances.So the
yc-app-clishould support mapping issues to different event types. While many settings likeOtherStringMappingscan be shared, however, theAlarmSettingmust be separated and users need to define them repeatedly (in fact, users can use spring's property placeholder to avoid declaring similar settings again and again)