7 posts tagged with "Jira"

Collecting attachments from many Jira issues can be tedious. The Simple Bulk Attachment Downloader app automates parallel downloads and packages attachments by issue for easy sharing and archiving.

When to use it​

• Migrating files during releases
• Gathering screenshots and logs for QA or support
• Archiving project assets before cleanup

Quick prerequisites​

• Jira Cloud account with the app installed
• Permission to view attachments in the issues

Step 1 — Filter the issues​

Use Jira issue navigator or a saved filter. Example JQL to find issues with attachments:

project = MYPROJECT AND attachments IS NOT EMPTY

Step 2 — Run the attachment analyzer​

Click the Simple Bulk Attachment Downloader action. The analyzer reports:

• Number of issues
• Total attachments
• Estimated download size

Step 3 — Download and organization​

Click Download X Attachments as ZIP. Files are organized as ISSUE-123 - Summary/attachments inside the ZIP.

Tips for large sets​

• Use date ranges (created >= -30d) to split exports
• Ensure enough local disk space before large downloads

Troubleshooting​

• If downloads stall: try smaller batches, clear browser cache, or use another browser
• If permission errors: confirm attachments are visible to your account

Internal links​

• User guide: /docs/Simple-Bulk-Attachment-Downloader-for-Jira/user-docs
• Export issues guide: /docs/Simple-Bulk-Issues-Excel-CSV-Export-for-Jira/user-docs

Suggested featured image: a ZIP file structure screenshot showing attachments organized by issue.

Excalidraw-powered whiteboards let teams sketch ideas directly inside Jira issues. This quick guide covers creating boards, saving snapshots, and sharing with team members.

Quick prerequisites​

• Jira Cloud with Excalidraw Diagrams plus Whiteboards app installed
• Permission to add app content to issues

Create a whiteboard​

• Open issue → click Excalidraw action → create new board
• Use shape libraries and templates for common diagrams

Collaboration tips​

• Locking & versioning: snapshot boards before edits
• Exporting: save as PNG/SVG for sharing

Internal links​

• User guide: /docs/Excalidraw-Diagrams-plus-Whiteboards-for-Jira/usage

Exporting Jira issues to Excel or CSV is useful for reporting, audits, and sharing issues with stakeholders. This guide walks through exporting filtered results using the Simple Bulk Issues Excel CSV Export app with practical JQL examples and field-selection tips.

Why use Simple Bulk Issues​

• Exports up to 1,000 issues with selectable fields
• Supports CSV, XLS and XLSX formats
• Preserves dates, users, multi-value fields and attachments metadata

Quick prerequisites​

1. Jira Cloud instance with the app installed and licensed
2. Permission to view issues you want to export
3. A saved filter or JQL query that returns the desired issues

Step 1 — Prepare your filter (JQL)​

Example: export all bugs in the last 30 days for PROJECT:

project = PROJECT AND issuetype = Bug AND created >= -30d

Tips:

• Test your JQL in Jira issue navigator first.
• Use saved filters for repeatable exports.

Step 2 — Open the export dialog​

Navigate to Issues → Search for Issues, run your filter, then click the Simple Bulk Issues Excel CSV Export action in the toolbar.

Step 3 — Select fields to export​

Choose only fields you need to keep file size manageable. Recommended fields for reporting:

• Key, Summary, Status, Assignee, Reporter
• Created, Updated, Resolution Date
• Priority, Issue Type, Labels, Components

Quick selection tips​

• Use “Select Default” for a compact report
• Use “Select All” for a complete data dump (beware of large files)

Step 4 — Choose format and export​

Select CSV, XLS or XLSX and click export. The file downloads automatically with a timestamped filename.

Handling large exports​

• For >1,000 issues, split your query (date ranges or project slices).
• Use XLSX for richer formatting; CSV is best for integrations.

Examples & automation​

• Automate exports by using saved filters combined with scheduled tasks that pull exported files from your team.

Internal links & resources​

• Read the full user guide: /docs/Simple-Bulk-Issues-Excel-CSV-Export-for-Jira/user-docs
• Related: Bulk Attachment Downloader: /docs/Simple-Bulk-Attachment-Downloader-for-Jira/user-docs

Suggested featured image: screenshot of export dialog with field selection.

Q: How to safely perform bulk edits? A: Run changes in a test environment, limit to manageable batches, and notify stakeholders.

Q: Reverting bulk changes? A: Use backups or audits; some operations can be reversed via automation rules if prepared.

Q: Performance when running bulk jobs? A: Stagger jobs during off-peak hours and monitor system load.

Q: Bulk export vs API? A: API exports can be scripted and retried; UI exports are simpler for ad-hoc needs.

Q: Permissions for bulk operations? A: Require appropriate Jira permissions; some bulk actions need project admin rights.

Q: Best practices? A: Document procedures, use saved filters, and split large jobs into smaller chunks.

Q: CSV fields mismatch after import? A: Ensure field order and delimiters match the target system; include header rows and consistent date formats.

Q: Special characters in CSV? A: Use UTF-8 encoding and quote fields containing commas or line breaks.

Q: Exporting custom fields? A: Some tools require explicit mapping for custom fields; ensure the export includes the raw field key.

Q: Large exports timing out? A: Split exports by date range or project; use background jobs where available.

Q: Preserving attachments in exports? A: Attachments are usually not embedded in CSV; include attachment URLs or use a separate attachment export.

Q: Automating exports? A: Use saved filters and automation scripts to schedule repeated exports.

Q: Why can't I download some attachments? A: You may lack view permissions for some issues or attachments are stored externally.

Q: Bulk downloader shows fewer files than expected. A: The app respects Jira permissions and only lists attachments visible to your account.

Q: Attachments missing after migration? A: Check attachment storage paths and link integrity; attachments may need reattachment after imports.

Q: Antivirus or proxy blocks? A: Network security appliances can block certain file types; whitelist domains if necessary.

Q: Attachment size limits? A: Jira imposes maximum attachment sizes; large files may be rejected at upload time.

Q: Best troubleshooting steps? A: Reproduce as a Jira admin, verify issue-level permissions, check attachment existence, and review audit logs.

Q: How to vet a plugin's security? A: Review vendor reputation, security policy, permissions required, and available source or audit reports.

Q: Principle of least privilege? A: Grant apps only the permissions they require; avoid global admin installs unless necessary.

Q: Data residency concerns? A: Understand where the plugin stores or processes data (cloud vs on-premise). Check privacy policy.

Q: Vulnerability disclosures? A: Prefer vendors with clear security contact and CVE or responsible disclosure program.

Q: Regular updates? A: Keep apps up-to-date and monitor release notes for security fixes.

Q: Sandbox testing? A: Test new plugins in a staging environment before deploying to production.