3 items
RTL support for Jira - detects Hebrew/Arabic text and sets direction automatically, per paragraph, with manual override. JIRA RTL makes Jira readable for Hebrew and Arabic speakers. Descriptions, comments, and edit fields get the right text direction automatically — no clicking, no setup. AUTOMATIC DIRECTION, PER PARAGRAPH • Every paragraph, heading, and quote follows the language of its own text: Hebrew aligns right, English stays left — in the same ticket • Lists and tables resolve as one unit, so all bullets and cells sit on the same side • Smart detection: the first strong character decides, unless the other script clearly dominates the text • Works while you type — direction follows each paragraph live in the comment and description editor, with no flicker PIN ANY FIELD WITH ONE CLICK Detection got it wrong? Every field carries a quiet, Jira-styled switch: ⇄ auto · → force RTL · ← force LTR. One click pins a direction for that field; clicking the pinned segment returns it to automatic. The switch follows Jira's light and dark themes, and you can hide it entirely from the popup. SIMPLE SETTINGS, INSTANT EFFECT One slider: auto on, or Jira's default left-to-right. Changes apply to open Jira tabs immediately — no page reload — and sync across your Chrome profile. WORKS WHERE YOU WORK Runs only on *.atlassian.net — issue descriptions, comments (viewing and editing), and text fields in Jira Cloud. PRIVATE BY DESIGN Everything runs locally in your browser. No data is collected or transmitted — the extension makes zero network requests. The only things it saves are your three settings (auto direction, switch visibility, on/off).
Jul 15, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.