ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #jira
Step‑by‑step guide to automate status transitions in Jira based on comment keywords, with prerequisites, configuration details, verification steps, and recovery tips.
Learn how to use Jira Automation’s scheduled trigger, JQL, and transition action to automatically close stale issues, with a step‑by‑step example and practical limits to watch.
Learn how to eliminate manual triage bottlenecks in Jira using the Trigger-Condition-Action framework to automate issue routing and project management.
A step‑by‑step guide to creating Jira Cloud automation rules that move issues between statuses automatically, with checks for permissions, audit logs, and rollback options.
Issues exist by direct URL but vanish from JQL and boards? That's Jira's Lucene index, not lost data. A diagnostic guide: confirm the symptom, isolate the cause, apply the right reindex, and know when to escalate.
Stop manually updating your Jira filters. Learn how to use JQL's historical operators and dynamic date functions to create self-maintaining project audits and dashboards.
Context A Jira Data Center upgrade fails during a sequential upgrade task, leaving the database in an intermediate state not matching any released version. Atlassian documents two recovery approaches: (1) restore the pre-upgrade database and <jira-home> from backup, or (2) fix the underlying issue and re-run the upgrade task. Constraint The maintenance
Goal Establish a repeatable development environment for Jira Software 8.20 that uses Docker to launch a clean instance and the Jira CLI to automate project creation, workflow import, and rule replication. Constraints The Docker image ‘atlassian/jira-software’ requires environment variables such as JIRA_DB_HOST and JIRA_DB_PASSWORD . The CLI plugin must match
When performing maintenance on a Jira Data Center instance, the primary goal is to rebuild the search index while minimizing the impact on end-user availability. There are two primary documented paths: Background Indexing and Full Re-indexing. Background Indexing allows users to continue accessing issue data by building a new index in a staging area, whereas
docker