ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Jira Align requires valid SSL/TLS certificates for secure communication with on-premise Jira instances. When utilizing self-signed certificates or those with incomplete CA chaining, the integration layer often reports generic connection errors within the Sync Status dashboard without granular TLS handshake details. This issue is exacerbated when the Jira Ali
Current behavior In Jira Align 8.0 the bulk import job endpoint ( /jobs ) accepts a cancel flag via POST /jobs/{id}/status . The UI can abort a job, but the API returns 405 for DELETE /jobs/{id} . When cancelled, the job status changes to cancelled while any records already written remain in the system. Timeout constraints Synchronous calls honor a client‑si
Portfolio hierarchy refresh behavior in Jira Align Jira Align surfaces real-time portfolio hierarchy roll-ups across value streams, but the refresh interval and scaling behavior for tenants running many concurrent value streams is not explicitly standardized in available documentation. The goal is to determine whether roll-up timing is fixed by the platform,
Goal: Ensure that rule‑based alert notification channel settings remain effective after a Jira Align major version upgrade without requiring manual re‑configuration. Uncertainty: Release notes indicate that alert rule notification channel preferences may reset after upgrades, but it is unclear whether this behavior applies to all subscription tiers, whether
Administrators configuring Jira Align dashboards can add widgets and adjust layout through the Administration → Branding and Themes screen, but the interface does not provide a setting to enforce a minimum color‑contrast ratio for custom widgets or themes. The goal is to guarantee that all user‑facing dashboard elements meet WCAG 2.1 AA contrast requirements
Integration goal Pull large work-item datasets from Jira Align into an external reporting system while keeping response times stable as the result set grows. Constraint Offset-based pagination forces the server to scan and discard rows before each offset, so latency rises with page depth. Cursor-based pagination avoids this only if the API exposes a stable m
Context Jira Align's GraphQL API uses Relay-style cursor pagination with a maximum first value of 100. Cursors are opaque base64-encoded strings that embed offset and sort information. Integration guides and support tickets indicate cursors expire after approximately 15 minutes of inactivity, though this timeout is not published in the public API reference a
WCAG 2.1 Conformance in Program Board Jira Align aims for WCAG 2.1 Level AA compliance, but current Accessibility Conformance Reports (ACRs) indicate gaps in interactive elements. A primary concern involves the Program Board, specifically regarding the movement and ranking of features and dependencies. Interaction Constraints The current interface relies hea
Jira Align's Jira Software connector is documented to skip records when it encounters an unrecognized Jira issue type or custom field type, logging a mapping error rather than failing the entire sync batch. Because unsupported fields are silently ignored rather than raising a hard error, excluded data may not be immediately apparent. The unresolved behavior
jiraalign