A schedule that provides a limit does not report the value of the limit in the activity stream in the entry for creation of the schedule. Subsequent edits of the limit field do report it.
Create a schedule that provides limit for a JT of "foobar"
now change it to "barfoo"
Now view activity stream
number 2 is ✅ , in UI:
{
"extra_data": [
"{}",
""
],
"limit": [
"foobar",
"barfoo"
]
}
number 1 is ❌ , the entry for creation exists, but does not report "foobar"
{
"description": "every day for 1 time",
"enabled": true,
"extra_data": "{}",
"id": 4,
"inventory": null,
"name": "asdffdsfe",
"rrule": "DTSTART;TZID=America/New_York:20181010T000000 RRULE:FREQ=DAILY;INTERVAL=1;COUNT=1",
"unified_job_template": "JobTemplate - DetailArt爩-397"
}
Reported modification of extra_data there could be argued to be another minor bug.
Tested by creating a schedule with a limit and the limit is reported in the creation entry of the Activity Stream, this has already been resolved.
ex:
{
"description": "a test to see if limit is in this entry",
"diff_mode": null,
"enabled": true,
"extra_data": "{}",
"id": 9,
"inventory": null,
"job_tags": null,
"job_type": null,
"limit": null,
"name": "rrrrr",
"rrule": "DTSTART;TZID=America/New_York:20200327T000000 RRULE:FREQ=MINUTELY;INTERVAL=1;COUNT=1",
"scm_branch": null,
"skip_tags": null,
"unified_job_template": "uselessjobtemplate",
"verbosity": null
}
Most helpful comment
Tested by creating a schedule with a limit and the limit is reported in the creation entry of the Activity Stream, this has already been resolved.
ex: