Level 2 · Lesson 0
Get ready for Level 2
Level 2 · Lesson 0A working Level 1 app, an Approved for Agent status, a Confluence space, Rovo, and two settings that tell the app where the kitchen is.
Behind, or starting here? Download the code as it should be before this lesson.
Level 2 opens a back kitchen in the same app. The head chef pastes the notes from a menu meeting on a page in Jira, and the app turns them into dish tickets, a page in Confluence, and work for an AI agent. It starts from the finished Level 1 app and uses more of your developer site.
Step 1: Start from a working Level 1 app
Locked until the step before it is done.
Open the Pad thai ticket and check the recipe card still shows a recipe. Everything in Level 2 is added to that same folder.
Starting fresh, or behind? Download the code from the link above, unzip it, and follow its README: npm install, forge register to make it your own app, then set the key and deploy. Keep your own manifest.yml if you already have one: its app.id is what makes the app yours.
Stuck? I can’t see the recipe card on the work item · The card says “No API Ninjas key”
Next step: next
Step 2: Add the Approved for Agent status
Locked until the step before it is done.
Lesson 5 hands dishes to an agent when someone moves them to a status with this exact name. On a team-managed board, a new column is a new status:
- Open the Kitchen board.
- Add a column and call it Approved for Agent, with that spelling and capitals.
On a company-managed space, add the status to the space’s workflow instead, or ask its admin to.
Next step: next
Step 4: Check Rovo is on
Locked until the step before it is done.
Lessons 6 and 7 add agents to Rovo, Atlassian’s AI assistant. Open Rovo Chat from the top bar of your developer site. If it is not there, ask your site admin to turn on Rovo, or create a new developer site that includes it.
Stuck? The specialist chef does not appear in Rovo
Next step: next
Step 5: Tell the app where the kitchen is
Locked until the step before it is done.
The back kitchen reads which Jira space and which Confluence space to use from two variables. They are not secrets, so they are not encrypted. Use your own keys if they differ:
forge variables set KITCHEN_PROJECT_KEY KIT
forge variables set MENU_SPACE_KEY MENU
forge variables listTickets are created as the Task type. If your Kitchen space has no Task type, also set KITCHEN_ISSUE_TYPE to one it has, such as Story.
You deploy in the next lesson, so there is no need to deploy now.
Stuck? I set or changed a variable · Creating a ticket fails with “Jira answered 400”
Next step: next