iPhone Dictation Not Working in Jira? 10 Fixes That Work

Short answer: In the Jira app on iPhone, dictation uses the mic on your keyboard, so a field must be open for editing. Tap into the summary, description or comment box until a cursor blinks. If your words vanish afterwards, the edit or comment was probably never saved.

You open Jira on your iPhone between meetings to write up a bug while the details are fresh, and you would rather talk it through than type it with your thumbs. You tap the mic on your keyboard and nothing happens. Or there is no mic. Or there is no keyboard at all, however many times you tap the ticket. Or you dictate a careful description, tap back to the board, and find the description empty when you look again. Or you post what you thought was a note for your team and realise the customer can see it.

On iPhone, dictation lives on the keyboard, and Jira only shows the keyboard while you are editing a text field. Most of a Jira work item (Jira's current name for what used to be called an issue) is not a text field. The status, assignee, priority, sprint, labels and dates are pickers. Only the summary, the description, the comment box and text-type custom fields take words, and several of them need to be saved before your words count.

So most Jira dictation problems on iPhone are about the keyboard, the field you are in and whether your edit was saved, not about your microphone. This guide works through every cause in order, starting with the most common. The same fixes apply to Jira on iPad. If dictation is failing in every app on your phone and not only in Jira, start with our complete guide to iPhone dictation not working instead.

Where the mic comes from in Jira

Jira's text fields have no dictation button of their own. On iPhone, the mic you dictate with is part of your keyboard. Apple's keyboard has one, and so do some third-party keyboards, including ours. You tap it, speak, and the words arrive at the cursor exactly as if you had typed them, so Jira treats them the same way it treats typing. Keyboard dictation does not need Jira to have microphone permission.

That leaves one big rule: if the keyboard does not appear, there is no mic to tap. Many "Jira dictation is broken" problems are really "no keyboard" problems, and most of the rest are about what happened to the words after they arrived.

The 30-second Notes test

Before you change anything, open the Notes app, create a new note, tap in the body so the keyboard appears, then tap the mic key and say a sentence.

• If dictation fails in Notes too, the problem is dictation on your iPhone, not Jira. Go to fixes 8 and 10.
• If it works in Notes but no keyboard appears in Jira, start with fix 1, then fixes 5 and 6.
• If the keyboard appears but has no mic, or the mic will not start, go to fixes 2 and 8.
• If your words arrived but were gone when you came back, go to fix 3.
• If your summary came out cut short or split, go to fix 4.
• If your words landed on the wrong work item, or in the wrong kind of comment, go to fixes 7 and 9.

The 10 fixes, in order

1. Tap into a field, not just the work item

Your home screen, notifications, boards and search results are places to find work, not places to write. Scrolling a board, dragging a card or opening a filter shows you work items, but nothing is being edited, so the keyboard stays down.

Tap a card to open the work item. It fills the screen, but opening it is not the same as editing it. Tap the summary at the top to change it, tap the description, including its placeholder text on an empty work item, to write the details, or tap the comment box to write a comment. Depending on your version, the description may open in its own editor. Either way, the keyboard slides up with a cursor where you tapped, and that is when the mic appears.

To create a new work item, use Jira's create button, pick the project and work type, and tap into the summary. The keyboard comes up with a cursor ready. Be careful where you tap on a board: pressing and holding a card lets you drag it to another column, which changes its status, so tap once and let go when all you want is to open it.

2. Find the mic key on your keyboard

If the keyboard appears but there is no mic, check which keyboard is showing. Apple's mic key sits at the bottom of Apple's keyboard, on the right on most current iPhones. Many third-party keyboards have no mic of their own, so if one of those is active there is nothing to tap. Tap and hold the globe key and switch to Apple's keyboard, or to a third-party keyboard that has a built-in mic.

Some fields bring up a different keyboard on purpose. Number fields, such as story points or estimates, may show a number pad, which usually has no mic key. Password boxes, including the sign-in page your company uses for Jira, always show Apple's own keyboard. Those are fields you type into rather than dictate into. If a third-party keyboard keeps switching back to Apple's in ordinary text fields, our guide to a third-party keyboard that keeps switching back explains why. Some companies also use mobile app policies, set through Atlassian or their device management, that can block third-party keyboards or restrict copy and paste inside work apps like Jira. If that is the case, your IT team holds the setting.

3. Save the description, and send the comment

This fix is about words that arrived but never stuck. Dictation puts words in a field. It does not save them. In Jira, an edit to the summary or the description only counts once it is saved, and a comment only exists once you post it.

• The description. Depending on your version, it opens in an editor with a save or done button. Leaving with the back button or swiping away before you tap it can discard what you dictated, or keep it only as a draft on your phone.
• The summary. An inline edit is saved when you confirm it. Tapping somewhere else in the middle of dictating can save half a sentence, or cancel the edit.
• Comments. Until you tap save or send, a comment is a draft on your phone. Nobody else can see it, and nobody is notified.

Make saving part of the rhythm: dictate, read it back, tap save or send, and only then move on. A weak connection causes a related problem. Jira saves your changes to its servers, so if your signal drops at the wrong moment an edit may not stick. If something you dictated is missing when you come back, check your connection and dictate it again.

4. Keep the summary to one short line

The summary is a single line, and Jira limits it to 255 characters. It is meant to be the title of the work, not the work itself. Two things go wrong when you dictate into it.

The first is starting to talk the moment a new work item opens. The cursor starts in the summary, so the whole bug report goes there, and it either gets cut off at the limit or leaves you with a title that fills the screen and an empty description. The second is line breaks. Saying "new line" or "new paragraph" inserts a Return, and a single-line field has no place for one. Depending on your version, Return can end the edit, which closes the keyboard and drops the rest of what you said.

Keep the summary to one short phrase, save it, then tap into the description and talk through the details there. The description is a multi-line editor, so a spoken line break starts a new line rather than ending your edit. iPhone dictation also adds a full stop at the end of a sentence, which looks odd in a summary. Delete it, or turn off Auto-Punctuation under Settings, General, then Keyboard.

5. Check your permissions and the work item's status

If you tap a field and no cursor appears, or the comment box works but nothing else will open, you may not be allowed to change what you are looking at. Jira admins decide who can browse a project, who can edit its work items and who can comment on them, and those rights can differ from project to project.

• Comment-only access. If you can comment but the summary and description will not open, you probably lack permission to edit work items in that project.
• A closed status. Some workflows lock work items once they reach a status such as Done or Closed, so fields stop opening even though you could edit them yesterday. Reopening the work item, if your workflow allows it, unlocks them.
• Service projects. In Jira Service Management, agents, customers and other team members see different things and can change different things. A customer view will not show the fields an agent can edit.
• The wrong site or account. If you belong to more than one Jira site, check that the app is on the site where you have the access you expect.

Ask a project admin to change your access if you need to edit. In the meantime, dictate your update as a comment, if you are allowed to comment, and let the assignee move it into the description.

6. Use text fields for words, and close pickers

Most of a work item is not free text. Tapping the status, assignee, reporter, priority, sprint, components or a dropdown custom field opens a picker, and while it is on screen the keyboard, and its mic, can disappear or stop sending text to the field you were in. People pickers usually have a search box, so words you dictate there filter the list instead of landing in the work item. Labels cannot contain spaces, so a dictated phrase there will not come out as one label. Date fields want a date from their picker, and number fields want a number.

The description and comment editors react to certain characters too. An at sign opens a list for mentioning a person, and while it is open your next words are treated as a search for whoever you are trying to mention. Dictation writes an at sign when you say it, and an email address brings one with it, so part of a sentence can vanish into the list or be swapped for a name. Depending on your version, a colon can open an emoji picker, and a line that begins like a list item can be turned into a formatted list.

If a list or picker opens, close it, then tap back into the text so the keyboard returns. It is usually easiest to dictate the words first, then set the status, assignee, priority and fields with a tap each, and add any @mentions by hand so the notification reaches the right person. Our guide to dictating quotes and special characters covers how to say symbols when you actually want them.

7. Check which work item, and which kind of comment

On iPhone a work item fills the screen, which makes it easy to lose track of which one you are looking at. Tapping a notification, a linked work item or a child work item opens that one instead, and a subtask looks a lot like its parent. The back button returns you through the items you opened, one at a time. Glance at the work item key and summary at the top before you speak.

Service projects add a second check. In Jira Service Management, the comment box can offer a reply the customer sees and an internal note that only your team sees. They look alike, and dictating an internal note into a customer reply shares it with the customer the moment you send it. Check which one is selected before you tap the mic, and read the comment back before you send it.

If your words went into the wrong place and are not saved yet, cut them and paste them into the right field. If you already posted a comment in the wrong place, edit or delete it from its menu, if you have permission to, and post it again where it belongs.

8. Free up the microphone

Dictation needs the microphone to itself. A phone or FaceTime call, a video call in another app, the camera recording a video to attach to a work item, or a recording app still running in the background can all keep hold of it, and dictation may refuse to start until they let go. Finish the recording, end the call, then try again.

Headphones are the next suspect. If the mic key does nothing, or dictation starts and gives up at once, disconnect your Bluetooth earbuds or headset and test with the iPhone's own microphone. If that works, the problem is the headset connection, not Jira. Our guide to iPhone dictation not working with AirPods walks through the headphone side.

9. Find words that landed somewhere else

If you dictated and the text seems to be missing, it usually went somewhere you were not looking. Check these in order:

• The summary instead of the description. If the cursor was in the summary, your details are in the title, possibly cut off at the limit (fix 4).
• An unsaved draft. Open the description or comment box again. Your words may still be sitting there, waiting for save or send (fix 3).
• A child work item, or the parent. The two pages look alike, so your words may be on the other one (fix 7).
• An internal note or a customer reply. In a service project, check both kinds of comment (fix 7).
• Search. If a search box was active, your words became a search, not a comment.
• A field you overwrote. If an old description was replaced, Jira keeps a history of field changes on each work item, which is easiest to browse from the work item's activity on the web.

And remember that dictation replaces any selected text, just as typing does. If a word was highlighted when you tapped the mic, what you said replaced it. Shake to undo straight away, then tap once where you want the new words so nothing is highlighted before you start again.

10. Check dictation on your iPhone

If dictation failed in Notes too, the problem is on the phone. Open Settings, go to General, then Keyboard, and make sure Enable Dictation is on. If the switch is missing or greyed out, check Screen Time: under Content & Privacy Restrictions, open the allowed apps list and make sure Siri & Dictation is allowed. A work iPhone may also restrict dictation through its management profile, in which case your IT team holds the setting.

Make sure the keyboard language matches the language you are speaking, since dictation follows the active keyboard. Then install any pending iOS update, update Jira from the App Store, and if nothing else has worked, restart your iPhone. A restart clears stuck audio sessions and keyboard processes in one step.

Jira quirks that look like broken dictation

• Dictation stops halfway through a thought. iPhone dictation stops when you pause. Our guide to iPhone dictation that keeps stopping explains what you can do about it.
• The keyboard closes while you are talking. Scrolling the work item or tapping outside the field can end editing, which closes the keyboard and stops dictation. Keep your thumb off the screen until your words have arrived.
• Work item keys come out as words. A key like PROJ-142 is not something dictation expects, so it comes out spelled out or split. Type or paste keys, and let Jira link them.
• Code and logs come out wrong. Stack traces, file paths and commands are not for dictating. Paste them into a code block and dictate the explanation around them.
• Your edit is on your iPhone but not on the web. Jira syncs through your account. Check that your phone is online and the edit was saved, then reload the work item in your browser.
• Names and jargon come out wrong. Service names, product codenames and team acronyms are the words general dictation handles worst. Read them back, because a ticket is read by other people.

Quick triage

• No keyboard when you open a work item: no field is being edited yet. Fix 1.
• Keyboard has no mic: a keyboard without a mic, a number pad, a policy, or dictation off. Fixes 2 and 10.
• Description empty when you come back: it was never saved. Fix 3.
• Summary cut short, or the keyboard closed mid-sentence: the 255-character limit or a spoken line break. Fix 4.
• Comment box works, description will not open: edit permission or a locked status. Fix 5.
• Mic vanished after tapping a field: a picker is open. Fix 6.
• Customer saw an internal note: the wrong comment type was selected. Fix 7.
• Mic starts then stops at once: microphone busy or Bluetooth. Fix 8.
• Words went missing: check the places in fix 9.
• Fails in Notes too: iPhone dictation settings. Fix 10.

Jira on iPhone versus Jira on Mac

On a Mac, Jira is usually a browser tab and you dictate with a keyboard shortcut rather than a mic key, so the usual traps there are browser microphone permissions, Jira's single-letter keyboard shortcuts firing when no field has focus, and inline fields saving half a sentence. Everything Jira does with your words is the same on both: the summary is one line, comments wait for you to post them, and permissions and workflows decide which fields you can change. Our guide to Mac dictation not working in Jira covers the desktop side, and our guide on how to dictate in Jira covers setup on both Mac and iPhone.

A dictation workflow that suits Jira

• Summary first, one phrase. Say what is wrong or what needs doing in a few words, then save it.
• Talk the description through. Context, steps to reproduce, what you expected and what happened instead. Speaking it tends to capture the detail that typing on a phone leaves out. Our guide to dictating bug reports has a structure that works well out loud.
• Save before you do anything else. Read it back, tap save, then move on.
• Set fields by tap. Status, assignee, priority, sprint and labels are quicker to pick than to say, and they avoid fix 6 entirely.
• Type keys and paste code. Dictate the prose around them.
• Check the comment type in service projects. Reply or internal note, every time.

It is worth getting right, because speaking is much faster than typing. Most adults type around 40 words per minute on a full keyboard, and even professional typists usually sit around 80 to 100, while normal speech runs at 130 to 150 words per minute. On a phone the gap is wider still, and it is the difference between filing a proper ticket from the corridor and leaving a one-line placeholder until you are back at your desk.

A keyboard with a mic that works in every project

Apple's dictation is free and built in, but it stops when you pause, it depends on settings that are easy to switch off by accident, and fixing a misheard word means going back and editing by hand on a small screen.

Voice Keyboard Pro is a custom iPhone keyboard with a built-in mic button for dictation in any iOS app, Jira included. Tap into a summary, a description or a comment box, tap the mic, speak, and your words are added at the cursor. Because it is a keyboard rather than a feature of one app, it works the same way in Jira, Notes, Messages and everywhere else you type. Like any keyboard, it only appears while Jira is editing text, and Jira still decides what gets saved and who can edit what, so fixes 1 and 3 to 7 still apply.

A few features help with ticket work in particular:

• Voice Edit lets you speak a change to fix text, so you can correct a version number or a name in a description without selecting and retyping it on a small screen.
• Two-way translation while dictating, across 24 languages, lets you speak in one language and write in another, which helps on teams whose working language is not everyone's first.
• Swipe typing is there for the moments when speaking out loud is not practical, such as an open-plan office or a quiet train.

Setup means adding the keyboard in Settings and allowing Full Access so it can reach the transcription service. Our guide to enabling Full Access for an iPhone keyboard explains what that permission does. On privacy, our servers store only operational pings. No audio and no transcript content is stored. There is a free tier with daily limits, and Pro is $4.99 a month or $34.99 a year. On a Mac, the same app lives in your menu bar: hold a hotkey, speak, release, and the text appears at your cursor in Jira or anywhere else.

Frequently asked questions

Why doesn't the keyboard appear in Jira?

Nothing is being edited yet. Opening a board or a work item shows it but does not start editing. Tap the summary, the description or the comment box, and the keyboard will appear with its mic.

Why did my dictated description disappear?

Most likely it was never saved. Depending on your version, the description has its own save or done button, and leaving without tapping it can discard your words. Open the description again, check for a draft, and save before you leave the work item.

Why can I comment but not edit the description?

You probably have permission to comment but not to edit work items in that project, or the work item is in a status your workflow locks, such as Done. Ask a project admin, or dictate your update as a comment in the meantime.

Does Jira need microphone permission for dictation?

No. Keyboard dictation is handled by your keyboard and iOS, not by Jira. Jira's microphone permission only matters for features inside Jira that record audio or video themselves.

Does this work the same way on iPad?

Yes. Jira on iPad uses the same keyboard-based dictation, the same fields and the same save and comment behaviour, so every fix here applies.

What to do next

Run the 30-second Notes test, then work through the fixes that match what you saw. For most people it is fix 1: a work item was open, but no field was being edited, so there was no keyboard and no mic. If your words were there and then gone, it is fix 3, and if a field simply will not open, it is fix 5. And if you want dictation that works the same way in every app on your phone, try Voice Keyboard Pro's free tier on your next ticket.