You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is similar to #7 but for VAlarm. Since we only support Display type of alarm without any repeating. So modelling of this alarm is simply:
make AlarmSetting a sealed interface of:
Triggered by a fixed datetime, using field mapping
Triggered by a duration, using field mapping, asking if the duration is positive or negative (since YouTrack doesn't support negative duration), also asking if it is related to either start or end
Triggered by a fixed duration, the duration can be either positive or negative, can be either related to start or end
the info will include a list of AlarmSetting instead of one AlarmSetting
⚠ One day event can not have a trigger related to the end date time. So the AlarmMapper should check if the ToBeMappedYouTrackIssueInfo has no EndDateTimeField instances and the trigger is related to dtend. If it is, discard such trigger
The text was updated successfully, but these errors were encountered:
Although there is a modelling (by using multiple interfaces) which can make one day event has to use AlarmTriggerSetting that is related to start datetime only, it is very complicated, and I would rather rely on the validator to avoid bad config
This is similar to #7 but for VAlarm. Since we only support
Display
type of alarm without any repeating. So modelling of this alarm is simply:AlarmSetting
a sealed interface of:AlarmSetting
instead of oneAlarmSetting
⚠ One day event can not have a trigger related to the end date time. So the
AlarmMapper
should check if theToBeMappedYouTrackIssueInfo
has noEndDateTimeField
instances and the trigger is related todtend
. If it is, discard such triggerThe text was updated successfully, but these errors were encountered: