SeeCodes Jira App settings

Give Jira admins one place to control the app.

The settings page lets Jira admins choose the supported SeeCodes route, confirm Forge-managed activation, manage one-time launch-link lifetime, and control the language used in task status and daily reports.
Forge-managed connectionUS / EU / UK routing1–14 day launch-link lifetime
Jira App overviewBoard progress badgesDocumentation

On this page

4 sections

A functional admin page, not a placeholder

The current settings page is built to handle routing, activation visibility, workspace preferences, and connection health in one Jira-native place.

Supported routing only

The current implementation supports only the default SeeCodes Forge remotes for US, EU, and UK routing. Jira App task starts use Forge auth, a strictly single-use Jira backend request key, and one-time launch codes rather than stored backend keys. The server rejects replays, binds each request key to the same tenant/session context, and rotates the next key only after a successful call.

Apps / SeeCodes Settings

SeeCodes Settings

Admin page

Connected

This Jira installation is active on https://dev.seecodes.com/eu.

Forge-managed activation

Preferences

Admins can control routing, secure link lifetime, and output language from one page.

Region Routing

US / GlobalEU (Stockholm)UK (London)

Base domain

https://dev.seecodes.com

Only https://dev.seecodes.com is supported here. EU and UK routing append /eu or /uk automatically. Direct execute-api URLs and custom backend domains are not supported for the Jira App path.

Link expiration (days)

14

Browser-facing launch links are configurable from 1–14 days if unused. After the IDE opens, the one-time launch code can be exchanged exactly once for a shorter-lived task permit.

Task & daily language

English

Used for generated AI task status updates and Daily writeups.

Save Preferences
Save Backend Route

Instance info

Connection health and activation details stay visible to the Jira admin.

Cloud IDf3b1…9ad2
Site URLacme.atlassian.net
Statusactive
Backend recognizedYes
Activation sourceForge-managed activation
Forge managedYes

Admin outcomes

The settings page keeps rollout and support conversations tighter.

  • • Keep region routing aligned with residency expectations.
  • • Confirm installation health without opening external tools.
  • • Standardize link lifetime and language across the team.

What the admin can control here

The current settings surface is built to make rollout, compliance, and day-to-day workspace administration easier.

Supported backend routing

Admins can choose the supported US, EU, or UK SeeCodes route instead of juggling custom backend URLs.

Connection and activation visibility

The page shows whether the installation is recognized, active, and Forge-managed so admins can understand connection health quickly.

Link expiration control

Set how long generated VS Code task links remain valid for developers after Jira launches them.

Task and daily report language

Choose the single language used for generated AI task status updates and the Daily writeup page.

Why this page matters

A strong admin surface makes the Jira App easier to adopt, easier to support, and easier to explain.
  • Onboard a new Jira site and point it at the correct supported region.
  • Verify that the backend recognizes the installation after setup or reconnection.
  • Standardize secure IDE link lifetime across the workspace.
  • Choose the language used in AI-generated task updates and daily writeups.
  • Read instance details when support, security, or compliance questions come up.

Helpful even when something is not healthy

If the backend has not recognized the installation yet or the connection needs attention, the same settings page can guide the admin through a reconnect or activation-pending state instead of leaving the setup ambiguous.