Jira Images: A Step-by-Step Guide to Adding Attachments
Need to add a jira image to an issue? Follow this step-by-step guide to upload, paste, or display it inline. Read now to learn how.
Adding an image to a Jira issue can make a bug, design question, or task much easier to understand. You can attach an image to an issue, place one inline in a description or comment, or paste a screenshot when your Jira editor supports it.
The confusing part is that these options don’t always behave the same way. An image may appear as an attachment instead of inside your text, or an upload may fail because attachments are disabled or restricted.
But here's the truth: you can usually add a Jira image in a few steps once you know where to put it. I’ll show you how to upload, paste, and display images, then cover common problems and practical ways to keep visual information useful.
How to Add an Image to a Jira Issue
Choose the method that matches how you want the image to appear: as an issue attachment, inside text, or in a comment. The exact button labels can vary by Jira version and editor.
- Open the Jira issue. Navigate to the task, bug, or request where the image belongs. Check that you can edit the issue or add comments.
- Attach an image to the issue. Look for the attachment or paperclip control, then select an image from your device. In some Jira experiences, you can drag an image onto the issue instead.
- Wait for the upload to finish. Keep the issue open until the image appears in its attachment area. If the upload stalls, check your connection and try again.
- Add an image inline when needed. To show an image within a description or comment, use the editor’s image option or paste an image into the editing area. An attachment may need to be inserted or selected in the editor to display inline.
- Save your changes. Submit the comment or save the issue description. If you only uploaded an attachment, confirm it appears on the issue.
- Check the result. Open the image to confirm it is readable and attached to the correct issue. Add a short caption or comment explaining what the image shows.
For example, attach a full screenshot to a bug report, then place a cropped view beside the relevant explanation. That gives teammates both the complete context and a quick visual reference.

Choose Between an Attachment and an Inline Image
An attachment is a separate image connected to the Jira issue. An inline image appears within a description or comment, which makes it easier to follow visual details alongside written steps.
Use an attachment when someone may need to open the full screenshot, compare several images, or keep a visual record with the issue. Use an inline image when the image supports a specific sentence, such as showing the button that fails.
Here's why: placement changes how quickly a teammate can understand the issue. A comment that says “the menu is broken” is less useful than one that shows the menu directly below the explanation.
If you aren’t sure, attach the original image and add a smaller inline view when the editor supports it. Avoid uploading duplicates unless each version has a clear purpose.
Where Jira Images Can Be Added
Jira images commonly appear in issue attachments, descriptions, and comments. The available options depend on your Jira version, editor, project settings, and permissions.
- Issue attachments: Add a screenshot, mockup, or reference image to the issue.
- Descriptions: Place an image beside the problem statement or acceptance criteria when the editor allows inline images.
- Comments: Add a new screenshot to clarify a discussion or show that a defect has changed.
- Work updates: Attach a visual when reporting test results or showing a completed change.
For example, a tester might attach the original screen and add a comment with a second image showing the error after a particular action. Keeping each image near its explanation makes the issue easier to review.
Make Images Easier to Understand and Review
A screenshot is most helpful when it shows the relevant detail without hiding the surrounding context. Crop unnecessary areas, but keep enough of the screen to show where the problem occurred.
Use a descriptive caption or comment, such as “Error appears after selecting Save.” If several images are attached, label their purpose in the surrounding text so teammates can distinguish the expected result from the actual result.
Before you upload, check for private information such as customer names, email addresses, access tokens, or account details. Blur or remove anything teammates don’t need to see.
The best part? A small amount of context can save several rounds of questions. One clear screenshot with a marked button and a short explanation often beats a long comment describing the same screen.
Troubleshoot Jira Image Upload Problems
If an image does not appear, first check whether the upload completed and whether the issue was saved. Then consider permissions, project settings, image size, and the editor you’re using.
- The attachment option is missing: You may lack permission to add attachments, or an administrator may have disabled attachments. Ask your Jira administrator to check the project and site settings.
- The upload fails: Try a smaller image and confirm that its format is supported in your Jira environment. Attachment size limits and accepted formats can vary.
- The image attaches but won’t appear inline: Open the editor’s image controls and insert the attachment into the text. An attached image does not always display automatically within a description or comment.
- The image looks unclear: Upload a sharper capture, crop it to the relevant area, or add a brief explanation identifying the important detail.
- The image is missing for a teammate: Confirm that the teammate can view the Jira issue and its attachments. Project permissions may restrict access.
Let me explain: changing the image repeatedly won’t fix a permission problem. If several people can’t attach images to the same project, ask an administrator to review its settings.
Jira Image Management Solution: ONES.com
ONES.com brings project management and knowledge management together in one platform, powered by ONES Assistant. ONES Project handles project work and is a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They’re sold separately, so you can choose the product that fits your team.

For teams that rely on screenshots and visual references, the challenge is often larger than uploading an image. People need to connect visual context to tasks, keep workflows clear, and help teammates find the right information later.
Core Capabilities
- Issue context gets scattered. ONES Project supports structured project work, helping teams keep task details and related discussion together. Result: Teammates have a clearer place to review work and its context.
- Existing Jira workflows are difficult to replace. Jira-compatible workflows help teams carry familiar processes into a Jira alternative. Result: Teams can transition without rebuilding every workflow from scratch.
- Different teams need different fields. Custom fields let teams capture details relevant to their work. Result: A bug report can include useful details such as device, browser, or test status.
- Standard task flows don’t fit every team. Custom workflows allow teams to shape how work moves between statuses. Result: Visual review and approval steps can fit the team’s process.
- Sprint work needs coordination. Sprint management helps teams plan and track iterative work. Result: Image-related tasks can be reviewed alongside other sprint items.
- Manual status updates take time. Automation can reduce repetitive workflow actions. Result: Teams spend less effort on routine steps and more on review.
- Progress is hard to see across tasks. Built-in reporting gives teams a way to review project activity. Result: Leads can identify work that needs attention.
- Extra plugins can add maintenance. Native capabilities can reduce reliance on plugins for common project needs. Result: Teams can simplify their project setup.
Application Scenarios
A software team can use ONES Project to manage bug reports with custom fields for browser, device, and severity. Testers can connect screenshots with the relevant task details and track work through a familiar workflow.
A team with strict network requirements can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment. ONES Project offers feature parity between cloud and self-hosted versions, and the free plan supports up to 30 seats.
ONES.com can suit teams that want project and knowledge management from the same vendor. Since ONES Project and ONES Wiki are sold separately, you can adopt either product independently.
Common Challenges When Adding Jira Images
- People can’t tell what an image shows. Add a descriptive caption or explain the key detail in the comment. For example, state which button was selected before the error appeared.
- Several similar images create confusion. Identify each image as an expected result, actual result, or follow-up capture. Remove redundant images when they no longer help explain the issue.
- Sensitive details appear in a screenshot. Review the image before upload and obscure personal or confidential information. If the image is already visible, follow your team’s process for removing it and sharing a corrected version.
- Teammates can’t access an attachment. Check that they can view the issue and that project permissions allow access. Ask a Jira administrator for help when the restriction affects multiple people.
FAQs About Jira Images
Can I paste an image directly into a Jira issue?
Often, yes. Open the description or comment editor and paste the image if your Jira editor supports it. You can also use its image control to insert an image. If pasting doesn’t work, attach the image through the issue’s attachment control, then check whether the editor lets you place that attachment inline.
Why does my image appear as an attachment instead of inside the comment?
Uploading an image and inserting it inline are separate actions in some Jira experiences. The upload connects the image to the issue, while the editor controls whether it appears within the text. Open the comment editor’s image options and select or insert the attachment. If you don’t see that option, your Jira version or editor may handle inline images differently.

Which image formats and sizes does Jira support?
Supported formats and maximum upload sizes can depend on your Jira version and administrator settings. Common formats such as PNG and JPEG are frequently used for screenshots, but check your environment’s accepted formats if an upload fails. Reducing image dimensions can help when an image exceeds a configured size limit.
Can I add an image to a Jira description after creating an issue?
If you have permission to edit the issue, you can usually update its description. Open the issue’s edit controls, use the editor’s image option if available, and save your changes. You may also attach an image separately and reference it in the description. The available controls can differ between Jira editors and deployments.
How do I make an issue screenshot more useful?
Show the relevant area, retain enough surrounding context to identify the screen, and add a short explanation of what happened. Mark the important detail when that helps, but avoid covering the content you want teammates to inspect. Before sharing, check for private information and remove anything unnecessary.
Conclusion
You can add a Jira image as an attachment, place it inline in a description or comment, or paste it when your editor supports that action. Choose the placement that makes the visual easiest to understand, then confirm it saved correctly.
When uploads fail, check permissions, project settings, image size, and editor behavior before trying the same action repeatedly. A clear caption, relevant crop, and quick privacy check can make each image more useful.
But here's the truth: the image itself is only part of a clear issue. Connect it to the task, explain what it shows, and keep related work easy for teammates to review.