[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-253448-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-253448-en":127},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","integrating-worksoft-certify-with-atlassian-jira","Integrating Worksoft Certify with Atlassian Jira","","Worksoft Certify® integration with Atlassian Jira® enables submission of failed steps from the Certify Result Viewer into Jira as editable defect-tracking issues. The integration tool generates a Jira issue from Certify result XML and images, populates issue fields using Certify process and results data, and imports the issue into Jira while returning an issue ID. Command line modes support help, metadata export, configuration storage, project/template creation, OAuth requests, and project listing, using either Basic Auth with API tokens or OAuth credentials.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/integrating-worksoft-certify-with-atlassian-jira/253448/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/integrating-worksoft-certify-with-atlassian-jira/253448.png","ImageObject",442,249,{"name":42,"@type":43},"Cart","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-11-01","2026-09-13",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",19,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"How does a failed step in Certify become a Jira issue?","Question",{"text":63,"@type":64},"In the Certify Result Viewer, users right-click a failed step and choose Send To > Jira. Certify generates a result XML and an image, which the Jira Integration tool uses to create and populate a new Jira issue.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"What fields are populated in Jira when the issue is created?",{"text":68,"@type":64},"The integration tool populates Jira issue fields using information from Certify process attributes and Certify results data. After creation, users can open Jira to further edit the issue.",{"name":70,"@type":61,"acceptedAnswer":71},"What authentication methods does the Jira integration support?",{"text":72,"@type":64},"The integration supports Basic Auth using an Atlassian API token and OAuth authentication. Configuration for both methods is stored in Certify via the SET_CONFIG mode.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},253448,1791407690,{"code":4,"msg":82,"data":83},"success",[84,88,93,98,103,108,113,118,123],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":86,"slug":87},11,90,"presentations",{"id":89,"doc_module":22,"doc_module_name":25,"category_name":90,"show_sort_weight":91,"slug":92},12,"Resumes",80,"resumes",{"id":94,"doc_module":22,"doc_module_name":25,"category_name":95,"show_sort_weight":96,"slug":97},14,"Invoices",70,"invoices",{"id":99,"doc_module":22,"doc_module_name":25,"category_name":100,"show_sort_weight":101,"slug":102},15,"Posters",60,"posters",{"id":104,"doc_module":22,"doc_module_name":25,"category_name":105,"show_sort_weight":106,"slug":107},16,"Social Media",50,"social-media",{"id":109,"doc_module":22,"doc_module_name":25,"category_name":110,"show_sort_weight":111,"slug":112},17,"Forms",40,"forms",{"id":114,"doc_module":22,"doc_module_name":25,"category_name":115,"show_sort_weight":116,"slug":117},18,"Letters",30,"letters",{"id":119,"doc_module":22,"doc_module_name":25,"category_name":120,"show_sort_weight":121,"slug":122},21,"Paper Templates",5,"papers-templates",{"id":124,"doc_module":22,"doc_module_name":25,"category_name":125,"show_sort_weight":4,"slug":126},158,"General","general-158",{"code":4,"msg":82,"data":128},{"doc_id":79,"user_id":129,"nickname":42,"user_avatar":130,"doc_module":22,"category_id":85,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":114,"language":136,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":12,"update_tm":140,"read_time":141},18829141979164,"https://eur-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","Integrating Worksoft Certify with Atlassian Jira  \nWorksoft Certify® integration with Atlassian® Jira® enables users to submit issues into Jira from the Certify Result Viewer. Jira is an IT defect management system that allows users to capture and organize IT issues, assign work, and follow team activities.  \nWith the integration software, you can create Jira issues and populate all of the issue fields using information from Certify results and processes. The issue is then imported into a Jira system, where you can edit and refine it. After the issue is submitted to Jira, you cannot see the details of the issue in Certify.  \nIntegration Architecture  \nThe following diagram shows an overview of how this integration works.  \nIn the Certify Result Viewer, a user right-clicks on a failed step and selects Send To > Jira. Certify generatesa result XML file and an image file that is sent to the Jira Integration tool.  \nJira Integration Command Line Modes  \nThe Integration tool completes the following tasks:  \n􀂋 Reads the result file and image file  \n􀂋 Generates a Jira issue  \n􀂋 Populates fields for the issue in Jira by using Certify process and results data  \n􀂋 Submits the issue to Jira which provides back an ID for a new issue  \n􀂋 Records the issue ID into the Certify database  \n􀂋 Launches Jira to allow users to do additional editing on the new issue  \nJira Integration Command Line Modes  \nThe Jira Integration tool is implemented using a standalone command line executable. This executable has the following modes of operation:  \n􀂋 Help  \n􀂋 GET_METADATA  \n􀂋 SET_CONFIG  \n􀂋 GET_CONFIG  \n􀂋 PROJECT  \n􀂋 CREATE_TEMPLATE  \n􀂋 REQUEST_OAUTH  \n􀂋 LIST_PROJECTS  \nWhen you start the Jira Integration executable without any arguments, you will see a summary of all the modes.  \nHelp Mode  \nThe Jira Integration executable, JiraIntegration.exe, starts in the Help mode. In this mode, Jira configuration stored in Certify is retrieved, and an attempt will be made to connect with the Jira system. Any conditions resulting in an error will be shown to the user.  \nJira Integration Command Line Modes  \nGET_METADATA Mode  \nUse the GET_METADATA mode to extract metadata from Jira and write it to a specified file. This mode is useful for retrieving details about fields from the back-end system, and it will most likely be used by someone editing fields in configuration data.  \nBefore performing this operation, you must have saved the Jira URL, user ID, and password in Certify through option SET_CONFIG. Certify uses these Jira credentials to establish a connection with the Jira System and retrieve meta data.  \nSET_CONFIG Mode  \nThe SET_CONFIG mode stores the configuration data from a specified XML file to a Certify database. The two authentication methods are supported by Jira integration:  \n􀂋 Basic Auth  \n􀂋 OAuth  \nBasic Auth Method  \nTo use the Basic Auth method, you must use an API token. API tokens are created and managed through the user's Atlassian account settings:  \n[https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/)  \nOAuth Method  \nTo use the OAuth method, see the “Configuring the Jira Connection” on page 11.  \nExample 1:\u003CDETAILS>  \n\u003CCredentials>  \n\u003CAuthenticationMode>BASIC\u003C/AuthenticationMode>  \n\u003CUSERNAME>myuserid\u003C/USERNAME>  \n\u003CPASSWORD>letmein\u003C/PASSWORD>  \n\u003CConsumerKey/>  \n\u003CVerifier/>  \n\u003CAccessToken/>  \n\u003CTokenSecret/>  \n\u003CPrivateKey/>  \n\u003C/Credentials>\u003C/DETAILS>  \nThis configuration saves Jira credentials into Certify. You must have at least this configuration saved in Certify before performing the GET_METADATA operation.  \nJira Integration Command Line Modes  \nExample 2:  \n\u003CDETAILS>\u003CMyProjectName>  \n\u003CFIELD>  \n\u003CFIELDSTRING>\"project\":{\"key\":\"CER\"}\u003C/FIELDSTRING>  \n\u003C/FIELD>  \n\u003CFIELD>  \n\u003CFIELDSTRING>\"summary\":\"{0}\"\u003C/FIELDSTRING>  \n\u003CVALUE_PATH>CertifyResults/LogTestStep/LogTestStepDetails/Narrative\u003C/VALUE_PATH>\u003C/FI","cbCaivH6XANOYLj2","https://ap.wps.com/l/cbCaivH6XANOYLj2","pdf",635500,"English","# Integration Architecture\n# Jira Integration Command Line Modes\n## Help Mode\n## GET_METADATA Mode\n## SET_CONFIG Mode\n## Basic Auth Method\n## OAuth Method","[{\"question\":\"How does a failed step in Certify become a Jira issue?\",\"answer\":\"In the Certify Result Viewer, users right-click a failed step and choose Send To \\u003e Jira. Certify generates a result XML and an image, which the Jira Integration tool uses to create and populate a new Jira issue.\"},{\"question\":\"What fields are populated in Jira when the issue is created?\",\"answer\":\"The integration tool populates Jira issue fields using information from Certify process attributes and Certify results data. After creation, users can open Jira to further edit the issue.\"},{\"question\":\"What authentication methods does the Jira integration support?\",\"answer\":\"The integration supports Basic Auth using an Atlassian API token and OAuth authentication. Configuration for both methods is stored in Certify via the SET_CONFIG mode.\"}]","Integrating Worksoft Certify with Atlassian Jira | PDF",1789266086,6]