Skip to content
Manually synchronize the status of the Jira issue › Understanding the Atlassian Jira integration with Vulnerability Response › Vulnerability Response integrations › Vulnerability Response › Unified Security Exposure Management › Security Operations
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Configure scheduler to update issues automatically

Configure the scheduler to update the Jira issues automatically for the records that have been added in the sn_vul_agile_tool_manifest table.

Before you begin

Role required: admin or schedule_admin.

About this task

All the records of the Application Vulnerable Item, Container Vulnerable Item, Application Remediation task and Container Remediation created in the sn_vul_agile_manifest table is considered for Jira issue update. If the record gets closed, and comments are added then those values also should get updated to the associated Jira issue.

Note:

  • The "update issues" scheduled job won’t update the Jira state if the workflow for the chosen agile issue project restricts any user from directly changing the state from another state.
  • If you close any entity record with additional comments, then only the last comment is considered at the time of update, and for the next update, all the comments are added to the associated Jira.

Procedure

  1. Navigate to All > System Definition > Scheduled Jobs > Update Jira Issues.

  2. You can modify the Run, Time zone, and Time fields in the Scheduled script.

FieldDescription
Run

Time interval to use for running the scheduled job:

  • Daily: Runs daily, at a designated time.
  • Weekly: Runs weekly, at a designated time and day.
  • Monthly: Runs monthly, at a designated time and day of the month.
  • Periodically: Runs on a designated repeating interval.
  • Once: Runs for a single occurrence only.
  • On Demand: Runs immediately on demand.
  • Business Calendar: Entry Start: Runs on the starting entry dates for the business calendar that you select in the field. A scheduled job runs for the starting date of each business entry you defined for the business calendar. For example, if the business calendar represents a fiscal year, and the starting date of each entry is a fiscal month, the scheduled job runs on the first day of each month.
  • Business Calendar: Entry End: Runs for the ending date for the business calendar you select in the field. This selection runs in the same manner as Business Calendar: Entry Start, but for the end dates of the associated business calendar entries. Note: When you select Business Calendar: Entry Start or Business Calendar: Entry End, you can apply an offset factor to schedule the job to run before or after the time span of the selected business calendar. To learn more, see the Offset Type and Offset fields.

To learn more about creating and using business calendars and defining business calendar entries, see and Create a business calendar Define business calendar entries.

DayDay on which the scheduled job should run. - If Run is set to Weekly, select the day of the week. For example, select Wednesday. - If Run is set to Monthly, select the day of the month. For example, select 25 for the 25th day of the month. This field appears only if you select Monthly or Weekly in the Run field.
Repeat IntervalDuration of the repeat interval for each scheduled job execution. Enter the duration in the number of days, hours, or minutes. For example: - To run the scheduled job every four days, enter 04 in the Days field. - To run it every 26 hours, enter 26 in the Hours field. - If it should repeat at an interval of 13:30:25, enter 13 in the Hours field, and then enter 30 and 25 in the two unlabeled fields after it.
TimeTime of day at which the scheduled job should run, expressed in hours, minutes, and seconds on a 24-hour clock. The selection that you make in the Time zone field determines the time zone for this entry.
Time zoneTime zone to use with the Time field entry when you specify the time at which the scheduled job should run. Select a time zone entry: - None: Use the default time zone for the logged-in user who is creating the scheduled job. For example, the scheduled job runs at 04:45 PM. US/Pacific time if it’s the user's assigned time zone, and you enter 16:45 into the Time field. - Use System Time Zone: Use the default system time zone that is specified for the instance in which it runs. For example, the scheduled job runs at 10:15 PM London time if Europe/London is the default system time zone for the instance, and you enter 22:15 in the Time field. - Actual time zone. - For example, the scheduled job runs at 1:30 PM in the US Eastern time zone if you select US/Eastern and enter 13:30 in the Time field.
run\_asBy default, the run_ as field value is empty. You can set the value to a domain user to create an issue for a specific domain.