{"type":"doc","content":[{"type":"layoutSection","content":[{"type":"layoutColumn","attrs":{"width":66.66},"content":[{"type":"paragraph","content":[{"text":"ModelOp Center seamlessly integrates with existing ticketing systems, such as JIRA, to allow enterprises to leverage existing IT investments.","type":"text"}]},{"type":"paragraph","content":[{"text":"Table of Contents","type":"text","marks":[{"type":"strong"}]}]},{"type":"extension","attrs":{"layout":"default","extensionType":"com.atlassian.confluence.macro.core","extensionKey":"toc","parameters":{"macroParams":{},"macroMetadata":{"macroId":{"value":"ff163f53-b5a6-4517-be43-f933de0c7607"},"schemaVersion":{"value":"1"},"title":"Table of Contents"}}}}]},{"type":"layoutColumn","attrs":{"width":33.33},"content":[{"type":"paragraph"}]}]},{"type":"heading","attrs":{"level":1},"content":[{"text":"Introduction","type":"text"}]},{"type":"paragraph","content":[{"text":"ModelOp Center provides the ability for the Model Life Cycle to create tickets within the existing Jira ticket system. The Model Life Cycle can create tickets corresponding to the manual steps and tasks required. This includes items such as approvals, reviews, tasks, and other activities in the Model’s Life Cycle. This guide details the steps to enable the integration.","type":"text"}]},{"type":"heading","attrs":{"level":1},"content":[{"text":"Jira Integration Setup","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Prerequisites","type":"text"}]},{"type":"paragraph","content":[{"text":"This guide assumes ","type":"text"},{"text":"moc-builder","type":"text","marks":[{"type":"code"}]},{"text":" has been installed. Please request download instructions for ","type":"text"},{"text":"moc-builder","type":"text","marks":[{"type":"code"}]},{"text":" ","type":"text"},{"text":"here","type":"text","marks":[{"type":"link","attrs":{"href":"https://www.modelop.com/contact/"}}]},{"text":". Before configuring ","type":"text"},{"text":"moc-builder","type":"text","marks":[{"type":"code"}]},{"text":", the Jira instance will need a service account created and configured to use an API token. To create an API Token, follow the documentation at ","type":"text"},{"text":"https://confluence.atlassian.com/cloud/api-tokens-938839638.html","type":"text","marks":[{"type":"link","attrs":{"href":"https://confluence.atlassian.com/cloud/api-tokens-938839638.html%7D%7B%5Ccolor%7Bblue%7D%5Cunderline%7Bhere%7D%7D"}}]},{"text":". This example assumes that the service account uses the email \"","type":"text"},{"text":"jira@modelop.com","type":"text","marks":[{"type":"link","attrs":{"href":"mailto:jira@modelop.com"}}]},{"text":"\". ","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"moc-builder Jira Configuration","type":"text"}]},{"type":"paragraph","content":[{"text":"The integration requires the ModelOp Center Gateway url and the url of the Jira instance to be integrated.","type":"text"}]},{"type":"paragraph","content":[{"text":"First, determine the external-ip of the Gateway. Set the Kubernetes context to the cluster and namespace that has ModelOp Center deployed. Run the following command: ","type":"text"}]},{"type":"codeBlock","attrs":{"language":"shell"},"content":[{"text":"kubectl get svc","type":"text"}]},{"type":"paragraph","content":[{"text":"The command will return an output like this:","type":"text"}]},{"type":"codeBlock","content":[{"text":"[johncarter@Johns-MacBook-Pro moc-builder (John@modelop-eks-test.us-east-2.eksctl.io:mocaasin)]$ kb get svc\nNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE\nengine-1 ClusterIP 10.100.72.22 8003/TCP 23h\nengine-2 ClusterIP 10.100.31.255 8003/TCP 23h\nengine-test ClusterIP 10.100.215.6 8003/TCP 23h\ngateway LoadBalancer 10.100.126.106 foo1.us-east-2.elb.amazonaws.com 8090:31166/TCP 23h\njupyter ClusterIP 10.100.242.107 8888/TCP 23h\nkafka ClusterIP 10.100.113.242 9092/TCP 23h\nminio ClusterIP 10.100.82.143 9000/TCP 23h\nmlc-manager LoadBalancer 10.100.145.82 foo3.us-east-2.elb.amazonaws.com 8085:31741/TCP 23h\nmodel-manager ClusterIP 10.100.205.30 8086/TCP,8088/TCP 23h\nmongodb ClusterIP 10.100.45.49 27017/TCP 23h\npostgres ClusterIP 10.100.77.22 5432/TCP 23h\nregistry ClusterIP 10.100.138.128 8761/TCP 23h\nreporting-service ClusterIP 10.100.38.87 8091/TCP 23h","type":"text"}]},{"type":"paragraph","content":[{"text":"The important value is the external-ip and port corresponding to the ModelOp Center Gateway. In this example, it’s ","type":"text"},{"text":"foo1.us-east-2.elb.amazonaws.com:8090","type":"text","marks":[{"type":"link","attrs":{"href":"http://foo1.us-east-2.elb.amazonaws.com:8090"}}]},{"text":".","type":"text"}]},{"type":"paragraph","content":[{"text":"NOTE: If the environemnt using ingresses instead of load balancers, run ","type":"text"},{"text":"kubectl get ing","type":"text","marks":[{"type":"code"}]},{"text":" and obtain the address corresponding to the ingress that points to gateway. Do not append the port number to the end of the address. That is only required if you are using the external IP from a service of type LoadBalancer.","type":"text"}]},{"type":"paragraph","content":[{"text":"Next, open the ","type":"text"},{"text":"config.json","type":"text","marks":[{"type":"code"}]},{"text":" file within ","type":"text"},{"text":"moc-builder","type":"text","marks":[{"type":"code"}]},{"text":"’s config directory and navigate to the ","type":"text"},{"text":"mlc-manager","type":"text","marks":[{"type":"code"}]},{"text":" section. It will contain the following:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"json"},"content":[{"text":"\"mlc-manager\": {\n ...\n \"env\": {\n ...\n \"modelop.gateway-url\": \"http://gateway:8090\",\n ...\n \"mlc.jira-task-monitor.url\": \"http://jira:8086\",\n ...\n },\n ...\n},","type":"text"}]},{"type":"paragraph","content":[{"text":"Change the value of the ","type":"text"},{"text":"modelop.gateway-url","type":"text","marks":[{"type":"code"}]},{"text":" env variable to be the location of gateway from above and change the value of the ","type":"text"},{"text":"mlc.jira-task-monitor.url","type":"text","marks":[{"type":"code"}]},{"text":" to be the location of the Jira instance. In this example, the Jira instance is located at \"","type":"text"},{"text":"https://foo.atlassian.net\"","type":"text","marks":[{"type":"link","attrs":{"href":"https://foo.atlassian.net%22).%5C%5C"}}]},{"text":".","type":"text"}]},{"type":"paragraph","content":[{"text":"Here is the example ","type":"text"},{"text":"config.json","type":"text","marks":[{"type":"code"}]},{"text":":","type":"text"}]},{"type":"codeBlock","content":[{"text":"\"mlc-manager\": {\n ...\n \"env\": {\n ...\n \"modelop.gateway-url\": \"http://foo1.us-east-2.elb.amazonaws.com:8090\",\n ...\n \"mlc.jira-task-monitor.url\": \"https://foo.atlassian.net\",\n ...\n },\n ...\n},","type":"text"}]},{"type":"paragraph","content":[{"text":"Go ahead and save the config file and open up the file located in ","type":"text"},{"text":"moc-builder","type":"text","marks":[{"type":"code"}]},{"text":" at ","type":"text"},{"text":"data/secrets.json","type":"text","marks":[{"type":"code"}]},{"text":". Here is how the file looks:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"json"},"content":[{"text":"{\n ...\n \"JIRA_USERNAME\": \"demo\",\n \"JIRA_PASSWORD\": \"modelop\",\n ...\n}","type":"text"}]},{"type":"paragraph","content":[{"text":"Change the ","type":"text"},{"text":"JIRA_USERNAME","type":"text","marks":[{"type":"code"}]},{"text":" value to be the email associated with the service account and the ","type":"text"},{"text":"JIRA_PASSWORD","type":"text","marks":[{"type":"code"}]},{"text":" to be the API token that was generated by Atlassian in the prerequisites step.","type":"text"}]},{"type":"paragraph","content":[{"text":"Here is the example:","type":"text"}]},{"type":"codeBlock","attrs":{"language":"json"},"content":[{"text":"{\n ...\n \"JIRA_USERNAME\": \"jira@modelop.com\",\n \"JIRA_PASSWORD\": \"API token goes here\",\n ...\n}","type":"text"}]},{"type":"paragraph","content":[{"text":"Next, create a new project in the Jira instance and note the key. Now update the key within the BPMN to be uploaded in ModelOp Center. For example, update the ","type":"text"},{"text":"NotficationToITSM.bpmn","type":"text","marks":[{"type":"code"}]},{"text":" BPMN within ","type":"text"},{"text":"moc-builder","type":"text","marks":[{"type":"code"}]},{"text":" to use the Project Key within the delegate: ","type":"text"}]},{"type":"codeBlock","attrs":{"language":"json"},"content":[{"text":"notificationAssignment.setJiraProjectKey(\"YOUR PROJECT KEY\");","type":"text"}]},{"type":"paragraph","content":[{"text":"Next, run the ","type":"text"},{"text":"moc-builder","type":"text","marks":[{"type":"code"}]},{"text":" compose and deploy commands to bring up the instance of ModelOp Center integrated with Jira.","type":"text"}]},{"type":"paragraph","content":[{"text":"Note: by default ModelOp Center's BPMN files only require the use of a \"Task\" issue type, so please confirm the Jira project has the Issue Type available. ","type":"text"}]},{"type":"paragraph"},{"type":"layoutSection","content":[{"type":"layoutColumn","attrs":{"width":66.66},"content":[{"type":"heading","attrs":{"level":3},"content":[{"text":"Related Articles","type":"text","marks":[{"type":"strong"}]}]},{"type":"paragraph"}]},{"type":"layoutColumn","attrs":{"width":33.33},"content":[{"type":"paragraph"}]}]}],"version":1}

Browser not supported