Configuration

Ticket Actions adds configurable buttons to Jira issues that launch predefined workflows:
  • Create sub-tasks
  • Create linked issue (can be in created in different project)
  • Set or update Checklist from Default Checklist or Smart Checklist Plugin.
Ideal for handling complex or non-standard business processes with consistency
App's configuration required advanced Administration knowledge.
We recommend to:
  • Involve System Administrators
  • Use test environments at first, to create proper configurations for your production environment.

General configuration

Move to manage Apps menu, find Ticket Actions app and click to configure
Project Administrators also able to edit limited configurations in frame of their projects from Ticket Actions tab in Project administration page
General tab contains main App's configuration. There you can select required subtasks engine:
  • Default checklists by Medeu IT or
  • Checklist by Smart Checklist App

Panel Tab

Panel Tab defines panel, which will appear in target tickets and contain action buttons for users
Title - name of panel
Projects - projects, included the panel
JQL Condition - condition for issues, where panel will be visible

Button Tab

Button Tab defines buttons, which will be available for users for trigger required actions
Text - Name of button
Weight - defenes buttons display order
Panel - defines panel, where button will be used
Groups - defines UM groups, that will able to use the button

Action Set tab

Action Set tab is mapping object between Buttons and Actions.

Name - technical name of action set
Series Field - non-mandatory field, that can be used in specific tests to take multiple values from Series Field (e.g. People) and use it for futhrer objects creation via ${seriesField} in JSON. It can create more then one object based on how many values from Series field on parent issue.
For example Change tasks for Change request are created based on Assigned Teams field. One change task will be created for every value from Assigned Team field.
Button - select Buttons, related to the action set
In Configuration tab (after creation):
Order - allows to define sequence for actions
Action - select Actions, related to the action set

Action tab

Action tab defines what will be triggered after running target action set. It can be:
  • Sub-tasks creation
  • Linked issues creation
  • Checklist creation
Name - technical name of action
Action Type - type of action
Projects - target project, where objects should be created
Properties - please check syntax examples below, and put own IDs and values to create target objects correctly

CHECK_LIST syntax example

# Subtitle 1
[T] To do
[P] In Progress
[D] Done
[R] Rejected
# Subtitle 2

SUB_ISSUE syntax example

{
        "issuetype": issueTypeId,
        "summary": "text",
        "description": "text",
        "priority": "${priority}",
        "reporter": "${reporter}",
        "customfield_...": "${Jira field id/mapping name/seriesField}"
 }

LINKED_ISSUE syntax example

 {
        "issuetype": issueTypeId,
        "summary": "${customfield_} : text",
        "description": "text",
        "security": "text",
        "customfield_": "${customfield_}",
        "assignee": "${customfield_}",
        "priority": "${priority}",
        "reporter": "${reporter}",
        "customfield_": "${customfield_}",
        "linkType": "relates to",
        "checklist": "[P] In Progress\n- [T] To do\n- [D] Done"
 }
After required Actions will be created, return to previous step Action Tabs, to link it with created actions

Mapping tab

Mappings allow to change value from base ticket to different value in subtask or linked issue.
Mappings creates as separated objects and can be used during added to JSON as ${mappingName} in SUB_TASK and LINKED_ISSUE
Name - name of mapping
Parent Field - target parent field
Project - related project
Mapping - mapping values, that will be used to define values from parent issue to subsidiary.Example:
assigneeGroupMap
Location1:Assignee Group1
Location2:Assignee Group2
Location3:Assignee Group3
Location4:Assignee Group4

After mapping creation you able to use it in JSON. Here is example:
 {
  "project": 12345,
  "issuetype": 3,
  "linkType": "is implemented by",
  "summary": "Terminate access CARD",
  "description": "Terminate ${customfield_12347} ACCESS CARD if exists in access control system and move it to 
left cards.",
  "priority": "${priority}",
  "reporter": "${reporter}",
  "customfield_12345": "${mappingName}",
  "customfield_12344": "${customfield_12346}"
 }