# How Engineering and DevOps can work together This walkthrough demonstrates how DuploCloud connects your existing engineering workflow — from a Jira ticket, through AI-assisted infrastructure provisioning, to a merged GitHub pull request — without leaving your tools. *** ## The Scenario An engineer needs to create storage for a new analytics feature. They raise a Jira ticket and assign it to the DevOps team. ![Product demo introduction](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-95bf12f882331963141a3998239a52735a097a29%2Fdemo2-01-intro.png?alt=media) *** ## Step 1 — Create a Jira Ticket The engineer creates a Jira ticket describing the request. ![Jira ticket created](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-5916ff37b4f313c6d0222e48d787597ca72303f2%2Fdemo2-02-jira-ticket-created.png?alt=media) They add a description: *"We need to create new storage for our order service analytics feature"* and assign it to the DevOps team. ![Jira ticket description](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-764a1c5166eb120986cbc674afa310d7020b59d7%2Fdemo2-03-jira-description.png?alt=media) *** ## Step 2 — Create a DuploCloud Ticket The DevOps engineer picks up the Jira ticket and creates a corresponding ticket inside DuploCloud to begin working on it. ![DuploCloud ticket created](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-1c7ae8d8a1759c52897716f662c79a7e89c20faf%2Fdemo2-04-duplocloud-ticket.png?alt=media) *** ## Step 3 — Agent Fetches Ticket Details The DuploCloud agent automatically fetches all details from the linked Jira ticket. ![Agent fetches Jira ticket details](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-7f37228335a1881490b12375eb7bdbe0fa3fd1f0%2Fdemo2-05-agent-fetches-details.png?alt=media) Since the task description is not fully specified, the agent identifies gaps and suggests clarification questions before proceeding. ![Agent suggests clarification questions](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-18eab8dbe2ea09aeb37969aa6289164c36a810e3%2Fdemo2-06-clarification-questions.png?alt=media) *** ## Step 4 — Post Questions to Jira The DevOps engineer reviews the suggested questions and approves them. DuploCloud automatically posts all questions back into the original Jira ticket. ![Questions posted to Jira](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-3823252dd56cf8387b0b2a70db6d5353a46b2cfa%2Fdemo2-07-questions-posted-to-jira.png?alt=media) Switching over to Jira confirms all questions are now visible on the ticket. ![Jira showing questions from DevOps](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-5731c9d64ad0115297c61423c906f15b712046eb%2Fdemo2-08-jira-shows-questions.png?alt=media) *** ## Step 5 — Engineer Answers in Jira The engineer reviews the questions and fills in the answers directly in Jira: * S3 bucket, \~100 MB * Production AWS environment * Write-heavy, low-latency, 90-day data retention * Used by the order service team ![Engineer filling answers in Jira](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-92d4595724406d035c85b5dc826abb6136022dd1%2Fdemo2-09-engineer-answers-jira.png?alt=media) ![Engineer submits answers](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-45b1546c50362968832c28a7e766d1a098be6569%2Fdemo2-10-engineer-submits-answers.png?alt=media) *** ## Step 6 — Back in DuploCloud: Check for Updates The DevOps engineer returns to DuploCloud and asks the agent if there are any updates. The agent checks the Jira ticket and reports back. ![DuploCloud checking for Jira updates](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-2e37cfd8bc48af624ca535549324d8e7c1339e9e%2Fdemo2-11-duplocloud-checks-updates.png?alt=media) The agent confirms the engineer has responded with answers to all the questions. The task can now proceed. ![Agent retrieves answers from Jira](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-cfe4ca7d36f50f57857e1375666eb9d2c66f47a0%2Fdemo2-12-agent-retrieves-answers.png?alt=media) *** ## Step 7 — Write Terraform and Create a Pull Request The DevOps engineer asks the agent to write the Terraform code for the task and open a pull request on GitHub. ![Asking agent to write Terraform and create PR](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-686ecfc614ed6a5b1932958c784cbac30520de4f%2Fdemo2-13-ask-agent-terraform-pr.png?alt=media) The agent completes the task autonomously. ![Task completed](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-fee9c7895386193b1f5eba168f9e8fbac26c15d8%2Fdemo2-14-task-completed.png?alt=media) *** ## Step 8 — Verify on GitHub Switching to GitHub confirms a pull request has been created. The branch contains all the files generated by the agent. ![GitHub branch with Terraform files](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-39daa1bff6780517286b6d27fbf69b3a4fc1ef85%2Fdemo2-15-github-branch-files.png?alt=media) *** ## Step 9 — Jira Updated Automatically Back in Jira, the ticket has been automatically updated with a link to the pull request — closing the loop without any manual steps. ![Jira ticket updated with PR link](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-e08a3e70d7d59056aebc28a3765aa1cdd69d1c14%2Fdemo2-16-jira-updated-pr-link.png?alt=media) *** ## Bonus — Works From Slack Too The entire workflow can be initiated from Slack. The DevOps engineer can start a session with DuploCloud via the Duplo Slackbot and complete tasks without ever leaving Slack. ![Slack integration](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-3250205a6a81b230c9d135dd3bb28f0edd202ed3%2Fdemo2-17-slack-integration.png?alt=media)