• Created by Unknown User (karolina.toman@coresoftlabs.com), last updated on May 13, 2015 5 minute read

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Each SLA Action responds to JIRA Issue Event. SLA Action can be assigned to additional parameters that decide if it will be executed.
Name of SLA Action will be visible in SLA History tab panel on view issue screen.
SLA Actions to perform:

  • Start
  • Pause
  • Resume
  • Finish
  • Cancel

Adding SLA Action

  1. Log in as a user with the JIRA Administrators global permission.
    Choose  > Add-ons. Select SLA PowerBox > SLA Configurations to open the SLA Configurations page.
    (info) Tip: Use Keyboard shortcut: g + g + start typing sla configurations
  2. Click the Add SLA Configurations button.
  3. Click Add Action button.
  4. Set the parameters (SLA Action, Priority, Issue Event) based on your needs.
  5. Click Add button.
  6. Added actions will be displayed on a set of tiles.

 

SLA Parameteres

Priority

On the value of the priority depends which action will happen if they are assigned to the same event:

  • High
  • Normal
  • Low

(info) Tip: By default priority is set as: Normal

If few actions have the same priority, they will be fired according to the specific sequence, which is:

  1. Start
  2. Cancel
  3. Finish
  4. Resume
  5. Pause

Issue Event

Action depends on occuring Issue Event. You can choose from the list below:

  • Issue Created
  • Issue Updated
  • Issue Assigned
  • Issue Resolved
  • Issue Closed
  • Issue Commented
  • Issue Comment Edited
  • Issue Comment Deleted
  • Issue Reopened
  • Issue Deleted
  • Issue Moved
  • Work Logged on Issue
  • Work Started on Issue
  • Work Stopped on Issue
  • Issue Worklog Updated
  • Issue Worklog Deleted
  • Generic Event

These are standard Events that are offered by JIRA. You can always define custom events.

Adding a custom event

  1. Log in as a user with the JIRA Administrators global permission.
  2. Choose  > System. Select Advanced > Events to open the View Events page.
    (tick) Keyboard shortcut: g + g + start typing events
  3. In the Add New Event form at the bottom of the page, add a Name and Description for the custom event.
  4. In the Template field, select the default email template to be associated with the event.
  5. Click the Add button.

The custom event must be associated with a default email notification template. A notification scheme configured to notify users of this event will use this email template when sending the notification. The custom event will appear in the list of events defined within the system. Initially, the event will be marked as inactive as it is not associated with a notification scheme or workflow post-function. Some events are fired by JIRA internally — e.g. an Issue Updated or Issue Moved event. Other events are fired from within workflow transition post-functions — e.g. an Issue Resolved event, or a Custom Events. All added custom events will be fired within workflow transition post-functions.

Configuring a post function to fire the custom event

  1. Log in as a user with the JIRA Administrators global permission.
  2. Choose  > Issues. Select Workflows to open the Workflows page, which displays all of the workflows in your system.
    (tick) Keyboard shortcut: g + g + start typing workflows
  3. Navigate to workflow transition post-function screen to be edited. See Configuring Workflow and  Applying Post Functions to Transitionsfor more information.
  4. Update the post function to fire the custom event.
  5. Activate or associate the workflow (and scheme) with the appropriate project. See Activating workflow for more information.

Additional parameters

There is a possibility to restrict launching actions only to the specific events. In order to do so you have to select basic fields (i.e. Issue type, Issue Status, Resolution Date) or define those parameters by using simple or advanced JQL. These features guarantee that:

  • action is fired only if it will be a result of a JQL Query
  • action is fired only if a JQL Query returns determined number of results
    • JQL can consists of tags such as i.e. $$ISSUEKEY$$, $$PROJECTKEY$$ that will be replaced with values of desired issue
  • action is fired only if the parameters of an issue - for which the action is fired - have certain values

Editing SLA Actions

  1. Log in as a user with the JIRA Administrators global permission.
    Choose  > Add-ons. Select SLA PowerBox > SLA Configurations to open the SLA Configurations page.
    (info) Tip: Use Keyboard shortcut: g + g + start typing sla configurations
  2. Click the Add SLA Configurations button.
  3. Choose desired Action from the tiles
  4. Click  > Edit
  5. Change desired parameters and click Edit button

Deleting SLA Actions

  1. Log in as a user with the JIRA Administrators global permission.
    Choose  > Add-ons. Select SLA PowerBox > SLA Configurations to open the SLA Configurations page.
    (info) Tip: Use Keyboard shortcut: g + g + start typing sla configurations
  2. Click the Add SLA Configurations button.
  3. Choose desired Action from the tiles
  4. Click  > Delete
  5. Confirm with Delete button

 

  • No labels