You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: If the field is a custom field, the configuration of the field.
1747
1747
type: Object
1748
+
- arguments:
1749
+
- description: 'A summary of the issue. Use issue fields as variables to enrich the text. Example: ${issue.name}.'
1750
+
name: summary
1751
+
prettyname: Summary
1752
+
required: true
1753
+
- description: The Jira project key where the issue will be created.
1754
+
name: project_key
1755
+
prettyname: Project Key
1756
+
required: true
1757
+
- description: 'Selects an issue type by name, for example: "Bug" or "Task".'
1758
+
name: issue_type_name
1759
+
prettyname: Issue Type
1760
+
required: true
1761
+
- description: 'A description of the issue. Use issue fields as variables to enrich the text. Example: ${issue.details}.'
1762
+
name: description
1763
+
prettyname: Description
1764
+
required: true
1765
+
- description: A CSV list of labels.
1766
+
isArray: true
1767
+
name: labels
1768
+
- name: priority
1769
+
description: Priority of the ticket.
1770
+
predefined:
1771
+
- 1 - High
1772
+
- 2 - Medium
1773
+
- 3 - Low
1774
+
- description: The due date for the issue (in the format yyyy-mm-dd).
1775
+
name: due_date
1776
+
- description: The name of the assignee. Relevant for Jira Server only. If you are using Jira Cloud, provide the assignee_id argument instead. Use the jira-get-id-by-attribute command to get the user's name.
1777
+
name: assignee
1778
+
- description: The account ID of the assignee. Relevant for Jira Cloud only. Use the jira-get-id-by-attribute command to get the user's account ID.
1779
+
name: assignee_id
1780
+
- description: The account ID of the reporter. Relevant for Jira Cloud only. Use the jira-get-id-by-attribute command to get the user's account ID.
1781
+
name: reporter_id
1782
+
- description: The name of the of the reporter. Relevant for Jira Server only. Use reporter_id for Jira Cloud. Use the jira-get-id-by-attribute command to get the user's name.
1783
+
name: reporter
1784
+
- description: The parent issue key (if you're creating a sub-task).
1785
+
name: parent_issue_key
1786
+
- description: The parent issue ID (if you're creating a sub-task).
1787
+
name: parent_issue_id
1788
+
- description: A text field for describing the environment in which the issue occurred. For example environment="IE9 on Windows 7".
1789
+
name: environment
1790
+
- description: The security level of the issue. For example security="Anyone".
1791
+
name: security
1792
+
- description: The component names of the issue. For example components="component1,component2". When using a Jira OnPrem instance, the entered components must already exist.
Copy file name to clipboardExpand all lines: Packs/MicrosoftTeams/Integrations/MicrosoftTeams/MicrosoftTeams.yml
+20
Original file line number
Diff line number
Diff line change
@@ -767,6 +767,25 @@ script:
767
767
If your instance configuration involves a Cortex XSOAR engine, provide the engine's IP (or DNS name) and the port in use in the following format - `https://IP:port` or `http://IP:port`.
768
768
For example - `https://my-engine.name:443`, `http://1.1.1.1:443`.
769
769
name: engine_url
770
+
- arguments:
771
+
- description: The channel to which to send messages. Supports only standard channels.
772
+
name: channel
773
+
prettyname: Channel
774
+
required: true
775
+
- description: 'The message to send to the channel. Use issue fields as variables to enrich the text. Example: “${issue.details}".'
Copy file name to clipboardExpand all lines: Packs/ServiceNow/Integrations/ServiceNowv2/ServiceNowv2.yml
+205-1
Original file line number
Diff line number
Diff line change
@@ -1683,14 +1683,218 @@ script:
1683
1683
required: true
1684
1684
description: Retrieves attachments from a ticket.
1685
1685
name: servicenow-get-ticket-attachments
1686
-
dockerimage: demisto/python3:3.11.10.116949
1686
+
- arguments:
1687
+
- description: 'Short description of the ticket. Use issue fields as variables to enrich the text. Example: “${issue.name}”.'
1688
+
name: short_description
1689
+
prettyname: Short Description
1690
+
required: true
1691
+
- auto: PREDEFINED
1692
+
name: ticket_type
1693
+
description: Ticket type.
1694
+
prettyname: Ticket Type
1695
+
predefined:
1696
+
- incident
1697
+
- problem
1698
+
- change_request
1699
+
- sc_request
1700
+
- sc_task
1701
+
- sc_req_item
1702
+
- sn_si_incident
1703
+
- std_change_template
1704
+
required: true
1705
+
- auto: PREDEFINED
1706
+
description: Ticket urgency. You can either select from the predefined options or enter another value. For example, "Urgent" or "5".
1707
+
name: urgency
1708
+
predefined:
1709
+
- 1 - High
1710
+
- 2 - Medium
1711
+
- 3 - Low
1712
+
- auto: PREDEFINED
1713
+
description: Ticket severity. You can select from the predefined options.
1714
+
name: severity
1715
+
prettyname: Severity
1716
+
required: true
1717
+
predefined:
1718
+
- 1 - High
1719
+
- 2 - Medium
1720
+
- 3 - Low
1721
+
- auto: PREDEFINED
1722
+
description: Ticket impact.
1723
+
name: impact
1724
+
predefined:
1725
+
- 1 - High
1726
+
- 2 - Medium
1727
+
- 3 - Low
1728
+
- auto: PREDEFINED
1729
+
description: Whether to set the ticket as Active.
1730
+
name: active
1731
+
predefined:
1732
+
- 'true'
1733
+
- 'false'
1734
+
- description: The ticket activity due date, in the format "2016-07-02 21:51:11".
1735
+
name: activity_due
1736
+
- description: List of users assigned to the ticket.
1737
+
name: additional_assignee_list
1738
+
- description: User assigned to the ticket.
1739
+
name: assigned_to
1740
+
- description: Category of the ticket.
1741
+
name: category
1742
+
- description: UID format.
1743
+
name: caused_by
1744
+
- description: Format type journal input.
1745
+
name: comments
1746
+
- description: Format type journal input.
1747
+
name: comments_and_work_notes
1748
+
- description: Company (UID format).
1749
+
name: company
1750
+
- description: Contact type.
1751
+
name: contact_type
1752
+
- description: Delivery plan (UID format).
1753
+
name: delivery_plan
1754
+
- description: 'Ticket description. Use issue fields as variables to enrich the text. Example: “${issue.details}”.'
1755
+
name: description
1756
+
prettyname: Description
1757
+
required: true
1758
+
- description: 'Ticket due date, in the format: YYYY-MM-DD HH:MM:SS.'
1759
+
name: due_date
1760
+
- description: 'Expected start date/time, in the format: YYYY-MM-DD HH:MM:SS.'
1761
+
name: expected_start
1762
+
- description: 'Follow up date/time, in the format: YYYY-MM-DD HH:MM:SS.'
1763
+
name: follow_up
1764
+
- description: UID format list (group).
1765
+
name: group_list
1766
+
- description: Location of the ticket.
1767
+
name: location
1768
+
- description: SLA of the ticket.
1769
+
name: made_sla
1770
+
- auto: PREDEFINED
1771
+
description: Whether to be notified about this ticket.
1772
+
name: notify
1773
+
predefined:
1774
+
- '1'
1775
+
- '0'
1776
+
- description: Order number.
1777
+
name: order
1778
+
- description: UID Format.
1779
+
name: parent
1780
+
- description: UID Format.
1781
+
name: parent_incident
1782
+
- description: UID Format.
1783
+
name: problem_id
1784
+
- description: UID.
1785
+
name: rfc
1786
+
- description: 'SLA due date/time, in the format: YYYY-MM-DD HH:MM:SS.'
1787
+
name: sla_due
1788
+
- description: Ticket subcategory.
1789
+
name: subcategory
1790
+
- description: The sys_id of the group to assign.
1791
+
name: assignment_group
1792
+
- description: The number that represents the incident state.
1793
+
name: incident_state
1794
+
- description: Ticket number.
1795
+
name: number
1796
+
- auto: PREDEFINED
1797
+
description: Priority of the ticket.
1798
+
name: priority
1799
+
predefined:
1800
+
- 5 - Planning
1801
+
- 4 - Low
1802
+
- 3 - Moderate
1803
+
- 2 - High
1804
+
- 1 - Critical
1805
+
- description: Template name to use as the basis to create new tickets.
1806
+
name: template
1807
+
- description: 'Custom (user defined) fields in the format: fieldname1=value;fieldname2=value; custom fields start with a "u_".'
1808
+
name: custom_fields
1809
+
- auto: PREDEFINED
1810
+
defaultValue: normal
1811
+
description: Type of Change Request ticket.
1812
+
name: change_type
1813
+
predefined:
1814
+
- normal
1815
+
- standard
1816
+
- emergency
1817
+
- description: 'State of the ticket, for example: "Closed" or "7" or "7 - Closed".'
1818
+
name: state
1819
+
- description: 'Date/time the ticket was opened, in the format: YYYY-MM-DD HH:MM:SS.'
1820
+
name: opened_at
1821
+
- description: 'Additional fields in the format: fieldname1=value;fieldname2=value;.'
1822
+
name: additional_fields
1823
+
- auto: PREDEFINED
1824
+
defaultValue: 'false'
1825
+
description: Flag that indicates whether to set field values using the display value or the actual value. 'true' treats input values as the display value. 'false' treats input values as actual values.
1826
+
name: input_display_value
1827
+
predefined:
1828
+
- 'false'
1829
+
- 'true'
1830
+
- defaultValue: ;
1831
+
description: The delimiter character to use as a separator for a list of fields in an argument for this command.
0 commit comments