Build one cross-project JQL filter and share it safely
Use a single saved JQL filter to view issues across multiple Jira projects, then share it with specific groups instead of Anyone.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use a single saved JQL filter to view issues across multiple Jira projects, then share it with specific groups instead of Anyone.
Native Jira Automation can replace repetitive manual toil and custom scripts—but it needs monitoring, version control, and respect for execution limits.
Decide when to use Jira Automation rules versus built-in bulk change for moving many issues through a workflow at once.
Enforce a Definition of Done checklist on Jira Cloud transitions using Automation, ScriptRunner, or Forge. Compare features, limits, and trade‑offs, and see a concrete Forge validator example with validation steps.
Inconsistent Jira intake creates manual cleanup and reporting noise. Encoding triage policy as declarative Automation rules reduces toil and enforces consistent components, priority and assignment without custom development.
Goal Determine how the auto‑generated release dates feature behaves when multiple teams share a program increment in Jira Align 2024.1, and whether the Jira Cloud integration can resolve or exacerbate overlapping release windows. Constraints The feature is documented to create consecutive release windows, yet reports indicate that overlapping dates can still
Context Jira Cloud delivers webhooks with an exponential-backoff retry policy documented only at a high level: retries continue for up to 14 days. The exact backoff intervals, jitter implementation, and the criteria that classify a delivery as permanently failed are not published. Goal Determine whether an integration can rely on deterministic retry timing f
On a low-traffic Jira Cloud instance, per-user licensing is the dominant recurring cost, and deactivating inactive accounts is the primary documented lever for releasing seats back to the subscription tier. The transition is not equivalent to removal, and that is where the tradeoff sits. A deactivated user stops consuming a license, but Jira keeps the accoun
Jira Cloud’s issue‑creation modal uses ARIA‑labelled buttons, but keyboard navigation sometimes skips the description field and the modal trap does not return focus to the Create button after closing via Escape. Automated scans also flag low contrast for priority dropdown icons. An internal design ticket debates whether the next major release should adopt WC