ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #jira
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
Goal I am planning the configuration of a Jira Data Center cluster (assume a recent 9.x LTS line) and want to bound how long a search on one node can return results that do not yet reflect an issue edit made on another node. Each node holds a local Lucene index copy, and changes propagate through the database-backed replication mechanism, so some staleness w
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
Jira Data Center and Server rely on a Lucene index for search, managed through the Index Manager. Documented failure conditions include IndexNotFoundException and CorruptIndexException appearing in atlassian-jira.log during startup or search operations. The Index Manager provides a Full Re-index option that rebuilds the index from the database, and a backgro
Context A Jira Data Center cluster uses a shared home directory with index replication enabled to keep search indexes consistent across nodes. Background indexing is active to avoid blocking user operations during re-indexing. Goal Achieve predictable search result parity across all cluster nodes immediately after a high-volume batch of issue updates, such a
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
In Jira Data Center, long-running REST API operations such as bulk changes or large issue exports are often processed via background worker threads. While the jira.rest.http.connectionTimeout setting governs the duration of the HTTP connection, there is uncertainty regarding how the application handles the loss of the client-side connection. When a client ab
Confluence ↔ Jira – Interoperability of regional time zones and date conversion Confluence stores all timestamps in UTC and renders them in the viewer’s timezone preference. The Date macro and Jira issue links both apply the current user’s timezone when displaying dates, but they do not retroactively adjust historical values when a user changes their timezon
The goal is to verify that moving an issue through its workflow on a Jira Scrum or Kanban board can be completed using only a keyboard, achieving functional parity with the drag‑and‑drop interaction. Constraints include potential differences between Jira Cloud and Jira Data Center UI, variations introduced by board filters, workflow schemes, issue‑type permi
qtest