From 65f11c9da8c6a81d92bf43b2495e6adeb212e1a8 Mon Sep 17 00:00:00 2001 From: jmcqueen Date: Fri, 21 Aug 2026 09:25:01 -0400 Subject: [PATCH] Clarify JIRA_BASE_URL is still required with JIRA_CLOUD_ID. Document that the site URL powers browse links in the poller Webex summary while the cloud gateway handles REST API calls. Co-authored-by: Cursor --- .env.example | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/.env.example b/.env.example index 63c48ae..3606d92 100644 --- a/.env.example +++ b/.env.example @@ -318,11 +318,14 @@ WEBEX_HOST_LICENSE_ID= # ----------------------------------------------------------------------------- # Jira (required for /jira* commands) -# Use JIRA_CLOUD_ID for service accounts / new Atlassian API gateway endpoints: +# JIRA_CLOUD_ID — service account / Atlassian Cloud API gateway (preferred): # JIRA_CLOUD_ID= # (constructs https://api.atlassian.com/ex/jira//rest/api/3 ...) -# Otherwise fall back to classic site base: -# JIRA_BASE_URL=https://your-org.atlassian.net +# JIRA_BASE_URL — your Jira site hostname (https://your-org.atlassian.net). +# Still required when using JIRA_CLOUD_ID: REST calls use the cloud gateway, +# but human browse links (e.g. poller Webex summary ticket keys) use +# JIRA_BASE_URL/browse/{KEY}. If unset, API may work but links won't click. +# If JIRA_CLOUD_ID is unset, JIRA_BASE_URL is also used for REST API calls. # ----------------------------------------------------------------------------- JIRA_CLOUD_ID= JIRA_BASE_URL=https://your-org.atlassian.net @@ -351,6 +354,8 @@ JIRA_MAX_RESULTS=30 # Webex space roomId to post the per-poll "N new tickets" summary to. # Poller stays DISABLED (cron never registered) if unset — safe default # for dev instances that share the same Jira credentials. +# Summary ticket keys link to JIRA_BASE_URL/browse/{key} — keep JIRA_BASE_URL +# set even when JIRA_CLOUD_ID handles API access. # # JIRA_POLLER_PRIME_ON_START # One-shot backlog-prime toggle. Set to `true` for a SINGLE deploy to