Filters

CLEAR ALL

Search Results ()

Filter Icon

Search Results ()

    All Plugins (171)

    Filter Icon

    Quick Info

    Product icon
    Product
    DevOps Velocity (HCL Accelerate)
    Plugin type icon
    Type
    plugin
    Compatibility icon
    Compatibility
    HCL DevOps Velocity version 3.0 or later
    created by icon
    Created by
    HCL Software
    Website icon
    Website
    Published Date
    July 24th, 2022
    Last Updated
    March 29th, 2024

    Description

  • Fetches the Jira issues, for each Jira issue plugin checks whether ChaRM ID is already there or not. If not, it creates a ChaRM ID for each issue.
  • In user input, user specifies Custom field name in Jira where they have stored Transport ID.
  • If Transport ID is not there, it can generate multiple Transport IDs in SAP as per requirement and then in Jira status changes to "In Development" using the ChaRM ID.
  • Jira status and HCL DevOps Velocity's VSM status changes as the SAP ChaRM ID's status changes.
  • ChaRM ID and Transport ID will be shown as "Description" in HCL DevOps Velocity.
  • Plugin will sync in every 5 min.
  • For assistance with plugin installation, contact the support team.
  • Quick Info

    Product icon
    Product
    DevOps Velocity (HCL Accelerate)
    Plugin type icon
    Type
    plugin
    Compatibility icon
    Compatibility
    HCL DevOps Velocity version 3.0 or later
    created by icon
    Created by
    HCL Software
    Website icon
    Website
    Published Date
    July 24th, 2022
    Last Updated
    March 29th, 2024

    ucv-ext-sap-charm:4.3.1.tar

    Uploaded: 23-Feb-2023 12:39

    Pull Command

    docker pull hclcr.io/accelerate/ucv-ext-sap-charm:4.3.1

    Release Notes

  • Minor plugin enhancements
  • ucv-ext-sap-charm:4.2.9.tar

    Uploaded: 22-Feb-2023 13:51

    Pull Command

    docker pull hclcr.io/accelerate/ucv-ext-sap-charm:4.2.9

    Release Notes

  • Minor Accelerate Description Enhancements
  • ucv-ext-sap-charm:4.2.8.tar

    Uploaded: 22-Feb-2023 08:18

    Pull Command

    docker pull hclcr.io/accelerate/ucv-ext-sap-charm:4.2.8

    Release Notes

  • Workflow modified
  • Automated features added
  • Multiple Transport ID enhancement
  • ucv-ext-sap-charm:2.2.1.tar

    Uploaded: 19-Dec-2022 09:12

    Pull Command

    docker pull hclcr.io/accelerate/ucv-ext-sap-charm:2.2.1

    Release Notes

  • Manage multiple Transport IDs
  • Jira UI improvements
  • ucv-ext-sap-charm:1.2.1.tar

    Uploaded: 15-Nov-2022 08:19

    Pull Command

    docker pull hclcr.io/accelerate/ucv-ext-sap-charm:1.2.1

    Release Notes

  • Added multiple Transport ID creation
  • Other fixes
  • ucv-ext-sap-charm:1.1.1.tar

    Uploaded: 11-Oct-2022 12:23

    Pull Command

    docker pull hclcr.io/accelerate/ucv-ext-sap-charm:1.1.1

    Release Notes

  • Added ATC checks and details
  • ucv-ext-sap-charm:1.0.3.tar

    Uploaded: 05-Sep-2022 18:17

    Pull Command

    docker pull hclcr.io/accelerate/ucv-ext-sap-charm:1.0.3

    Release Notes

  • Minor Improvements
  • ucv-ext-sap-charm:1.0.2.tar

    Uploaded: 01-Sep-2022 12:57

    Pull Command

    docker pull hclcr.io/accelerate/ucv-ext-sap-charm:1.0.2

    Release Notes

  • Initial release syncs SAP Normal changes with Jira issues
  • ucv-ext-sap-charm:1.0.1.tar

    Uploaded: 01-Sep-2022 11:15

    Pull Command

    docker pull hclcr.io/accelerate/ucv-ext-sap-charm:1.0.1

    Release Notes

  • Initial release syncs SAP Normal changes with Jira issues
  • Overview

    • Plugin sync SAP Normal Changes in SAP’s Change Request Management with Jira issues.
    • Fetch all Jira issues using the provided JQL Query, for each Jira issue plugin checks whether Charm ID is already there or not. If not, it creates a Charm ID for each issue.
    • In user input, user specifies Custom field name in Jira where they have stored Transport ID.
    • If Transport ID is not there, then in SAP status changes to “In Development” using the Charm ID.
    • Jira status and HCL DevOps Velocity’s VSM status changes as the SAP Charm ID’s status changes.
    • Charm ID and Transport ID will be shown as “labels” in HCL DevOps Velocity.
    • Plugin will sync in every 5 min.

    Configuration Properties

    The following tables describe the properties used to configure the integration. Each table contains the field name when using the user interface and the property name when using a JSON file.

    • The General Configuration Properties table describes configuration properties used by all plugin integrations.
    • The SAP chaRM Configuration Properties table describes the configuration properties that define the connection and communications with the SAP.

    Some properties might not be displayed in the user interface, to see all properties enable the Show Hidden Properties field.

    General Configuration properties
    Name Description Required Property Name
    NA The version of the plugin that you want to use. To view available versions, click the Version History tab. If a value is not specified, the version named latest is used. No image
    Integration Name An assigned name to the value stream. Yes name
    Logging Level The level of Log4j messages to display in the log file. Valid values are: all, debug, info, warn, error, fatal, off, and trace. No loggingLevel
    NA List of plugin configuration properties used to connect and communicate with the SAP. Enclose the properties within braces. Yes properties
    The name of the tenant. Yes tenant_id
    NA Unique identifier assigned to the plugin. The value for the Jira plugin is ucv-ext-sap-charm. Yes type
    HCL DevOps Velocity User Access Key An auto-generated user access key provides credentials for communicating with the HCL DevOps Velocity server. Yes NA

    SAP ChaRM Configuration Properties
    Name Type Description Required
    SAP Url (ES1) String The base URL of the SAP ES1 server. Yes
    SAP Url (N09) (Optional) String The base URL of the SAP N09 server if ATC Checks are required else leave it empty. No
    SAP User String The SAP user name. Yes
    SAP Project String The SAP project name. Yes
    SAP Custom Field Mapping Multiline Map Jira custom fields for storing SAP data in Jira, eg -> {“sap_user”: “SAP User V2″,”sap_charm_id”: “SAP CharmID V2″,”customizing_transport_id_count”:”Customizing Transport ID Count”,”workbench_transport_id_count”:”Workbench Transport ID Count”,sap_cycle_id”: “SAP CycleID V2″,”sap_project”: “SAP Project V2″,”sap_landscape_id”: “SAP Landscape ID V2”} Yes
    Personal Access Token String Personal Access Token to authenticate with the Jira server. If supplied, Username and Password will be ignored.
    NOTE: For Jira cloud version provide username and password. For Jira server provide personal access token.
    No
    Access Token String The Access Token for OAuth authentication. If supplied, Personal access token, Username and Password will be ignored. No
    Access Token Secret String The Access Token Secret for OAuth authentication. If supplied, Personal access token, Username and Password will be ignored. No
    Consumer Key String The consumer key for oauth authentication with the Jira server. If supplied, Personal access token, Username and Password will be ignored. No
    Consumer Secret String The consumer secret for oauth authentication with the Jira server. If supplied, Personal access token, Username and Password will be ignored. No
    jiraProjects Array A list of Jira Project Keys separated by commas. Example: PROJ1, PROJ2′ Yes
    JQL Query String JQL Query has higher priority than Project Keys . If JQL Query is added , Project Keys will not work . No
    Proxy Server String The URL of the proxy server including the port number. No
    Proxy User Name String The user name used to authenticate with the proxy server. No
    Proxy Password String The password used to authenticate with the proxy server. No
    URL String The base URL of the Jira server. Yes
    User Name String The user name used to authenticate with the Jira server. No
    Password Secure Password to authenticate with the Jira. If supplied, Personal access token will be ignored.
    NOTE: For Jira cloud version the Access Token should be entered in the Password field.
    No
    requestTimeout Number Timeout (in seconds) to apply to each request to the Jira server. Range is 10 to 150 seconds No
    Custom Field Mapping Multiline Map Jira fields to the fields expected by this server as a Name Value pair, eg: “Epic Link”: “Epic field in Jira”, “Sprint”: “Sprint field in Jira”, “Story Points”: “Story field in Jira. Yes