# From invite to merged PR

A step-by-step walkthrough for a developer: accept an invite, find your repos, make a task from a ticket and start a session on it.

This walkthrough follows Omar, a developer who joins Northwind. He accepts the invitation, lets the desktop app find
his clones, turns a ticket into a task on the board and starts a session on that task. The session is where the work
toward a merged pull request happens.

1. Omar accepts the invitation.

   ![Step 1](/walkthroughs/j2/J2.01.light.webp)

2. Off-app navigation: Omar installs the desktop app, signs in from Home’s space switcher, approves its device code in the system browser, then opens Repos and chooses Find on this machine. The Installer chapter follows each action.

   ![Step 2](/walkthroughs/j2/J2.02.light.webp)

3. Omar explicitly searched with Find on this machine. Confirm the matched clones; no repository binds before confirmation.

   ![Step 3](/walkthroughs/j2/J2.03.light.webp)

4. Review Assigned to Omar, then make a task from a ticket.

   ![Step 4](/walkthroughs/j2/J2.04.light.webp)

5. He pastes the ticket's link. The task keeps only the link and the key, never the ticket text, and the branch will carry the key.

   ![Step 5](/walkthroughs/j2/J2.05.light.webp)

6. The new task shows the ticket's link and key. His harness reads the ticket itself, through its own Jira connection.

   ![Step 6](/walkthroughs/j2/J2.06.light.webp)

7. Choose the SDD workflow for the task.

   ![Step 7](/walkthroughs/j2/J2.07.light.webp)

8. The selected SDD workflow is visible. Open the branch/worktree choice.

   ![Step 8](/walkthroughs/j2/J2.08.light.webp)

9. New worktree is already selected; start Checkout header in that worktree.

   ![Step 9](/walkthroughs/j2/J2.09.light.webp)

[Read the guide](/guides/start-a-session)

## What you just saw

- **Find on this machine** looks for clones of your org's repos in the desktop app. Nothing is linked until you
  confirm the matches.
- **A task from a ticket** keeps only the ticket's link and key, never its text. The branch carries the key, and your
  harness reads the ticket through its own connection.
- **A session on a task** can follow a workflow, and can work in its own copy of the repo (a git worktree), so it never
  overwrites edits you are making in your checkout.

Next steps: [Start a session](/guides/start-a-session) covers harnesses, modes and context,
[Workflows, gates and the board](/guides/workflows-and-the-board) explains tasks and gates, and
[From idea to merged PR](/scenarios/idea-to-merged-pr) follows the work through review to the merge.
