Why Scheduled Job not captured in Update set

[abhijeetpaw]

Hello Experts,

I want to know the reason why scheduled jobs and transnational data such as incidents, changes, problems, knowledge, and CI's

are not captured in the update set.is there any specific reason for that can one please guide them on this?

Thank You

[jtshone]

I cannot understand why this isn't captured by default.  The scheduled job contains code, it is not data.

[jamesmillet]

I agree with jtshone....Scheduled job are automation code that we develop. I just lost 2 days of code updates from clone activity, as I expected the updates to be in the update set that I exported before the clone!

[BrianD502676804]

It could be argued (and I often do) that records like Scheduled Job definitions (sysauto) are much more like a configurational record than transactional one. Once established, they are not being changed by normal processing similar to the triggers that rely on them (sys_trigger), they only change when a developer makes and saves that change in configuration. That they get captured as an update if you export/import them as XML shows that they are treated differently from most "data" records, like Groups/Users/Schedules/etc. (Schedules are another one I would argue has more value being captured than not).

I really wish SN would change their default behavior here, since as mentioned it often can lead to loss of work and really has no upside as-is that I can see, with not capturing by default.

Hopefully, the Enhancement angels are listening.

-Brian