ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #jira
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.
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
We need to migrate a small application’s test artifacts from an existing qTest instance to a new deployment while keeping the system online. The goal is to preserve continuity for both test execution and defect tracking in Jira. The primary constraint is the lack of a single‑transaction migration path. qTest’s REST API supports incremental pulls via the modi
docker
qtest