Associating multiple work items to a commit in DevOps

  • Release version: Yokohama
  • Updated July 31, 2025
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Associating multiple work items to a commit in DevOps

    ServiceNow DevOps supports associating multiple work items to a single commit across popular platforms including Azure DevOps, Bitbucket, GitHub, and GitLab. This feature enables customers to link development work effectively with related work items, enhancing traceability and process alignment.

    Show full answer Show less

    Key Features

    • Supported Commit Message Formats: DevOps parses work item IDs from commit messages using predefined patterns such as colon-separated lists (e.g., "STRY1, STRY2:"), hash-prefixed identifiers (e.g., "#STRY1"), and Jira-style keys (e.g., "JRA-123").
    • Customizable Parsing Logic: Customers can extend or customize the work item extraction logic by modifying the DevopsCommitMessageParser script include, which inherits from DevopsCommitMessageParserSNC. This allows support for additional message formats tailored to organizational processes.
    • Example Custom Pattern: The documentation provides a sample implementation for a custom regex pattern that recognizes work item IDs within square brackets (e.g., "[STRY1]"). This demonstrates how to extend parsing logic via script includes.
    • User Interface Support: Beyond commit message parsing, linking work items to commits can also be done through the Azure DevOps UI. Customers can view associated work items directly in the DevOps commit record and pipeline interfaces within ServiceNow.

    Practical Use for ServiceNow Customers

    This capability allows customers to:

    • Automatically associate multiple work items with commits, ensuring accurate traceability between development activities and related tasks or bugs.
    • Customize commit message parsing to align with internal naming conventions or workflows, enhancing integration fidelity.
    • Leverage both automated commit message parsing and manual linking via Azure DevOps UI for flexible workflows.
    • View and manage linked work items conveniently within ServiceNow’s DevOps Commit records and pipeline views, facilitating better monitoring and reporting.

    Multiple work items for a commit are supported in DevOps for Azure DevOps, Bitbucket, GitHub, and GitLab.

    Work item syntax in the commit message can be customized to reflect the processes in your organization using the DevopsCommitMessageParserSNC script include in the System Definition > Script Includes module.

    In order to link the commits with work items, the work item native ID is extracted from the commit message. In the base system, DevOps supports following commit message formats:
    /**
         * Supported patterns
         * Colon pattern 
             * Sample supported formats: 
                 *   1. STRY1,STRY2: Additional bug fixes
                 *   2. STRY1 , STRY2 : Additional bug fixes
                 *   3. STRY1, STRY2 : Additional bug fixes
         * Hash pattern 
             * Sample supported formats: 
                 *   1. Fixes for #STRY1, #STRY2, #STRY3
                 *   2. Fixes @$#3 and #1 work item
                 *   3. Fixes for #STRY1 #STRY2 #STRY3
                 *   4. Fixes for AB#123
         * Jira pattern
             * Sample supported formats: 
                 *   1. JRA-123 fixed
                 *   2. JRA-123 JRA-234 JRA-345 resolved
         */
    If you want to add support for additional message formats to meet the processes in your organization, you can add a custom logic in the DevopsCommitMessageParser script include by navigating to the System Definition > Script Includes module. DevopsCommitMessageParser script include extends from DevopsCommitMessageParserSNC. The DevopsCommitMessageParserSNC has three regular expressions defined for identifying work item native IDs for supported message formats in the base system. See the following example to include a new custom message format that has work item native IDs in square brackets.
    var DevopsCommitMessageParser = Class.create();
    DevopsCommitMessageParser.prototype = Object.extendsObject(DevopsCommitMessageParserSNC, {
        initialize: function() {
            DevopsCommitMessageParserSNC.prototype.initialize.call(this);
            this._customPattern = /\[(.*?)\]/g; // The regex pattern to match the words written inside square brackets.
            // Example commits message to match this custom pattern is : "[STRY1], [STRY2] Additional bug fixes"
        },
        getWorkitemsFromCommitMessage: function(message, branchName) {
            var workitems = [];
            // We first call the getWorkitemsFromCommitMessage method from the parent class to get the matching workitems ids for OOB formats
            var defaultWI = DevopsCommitMessageParserSNC.prototype.getWorkitemsFromCommitMessage.call(this, message, branchName);
            if (!gs.nil(defaultWI) && defaultWI.length > 0) {
                workitems = workitems.concat(defaultWI);
            }
            // Now call your custom method that returns an array of workitem native IDs matching custom pattern
            var customWI = this.getWIFromCustomPattern(message);
            if (!gs.nil(customWI) && customWI.length > 0) {
                workitems = workitems.concat(customWI);
            }
            // getUniqueWorkItems method from parent class removes duplicates from the workitems array
            workitems = this.getUniqueWorkItems(workitems);
            // return the final list
            return workitems;
        },
        getWIFromCustomPattern: function(message) {
            var wi = [];
            var l;
            var match;
            var matches = message.match(this._customPattern);
            if (gs.nil(matches))
                return wi;
            for (var i = 0; i < matches.length; i++) {
                l = matches[i].length;
                match = matches[i].substring(1, l - 1); // trim the brackets
                wi.push(match);
            }
            return wi;
        },
        type: 'DevopsCommitMessageParser'
    });

    Linking work items to a commit using the Azure DevOps user interface is also supported in DevOps. Link work item to a commit in Azure DevOps

    You can view the list of associated work items in the DevOps Commit record, and in the Pipeline UI.