Export the Jira issues you find with JQL to a PDF (one issue per page) or an Excel workbook. Custom fields, comments and the attachment list are included. The files are built in your browser; issue data is never sent to GRAMSHIFT or to third parties.
ORDER BY on its own is not accepted.
project = ABC ORDER BY key project = SUP AND created >= -30d key in (ABC-12, ABC-15) filter = 10042
You see only the issues and fields that your own Jira permissions allow. The app cannot edit issues.
| Excel | ||
|---|---|---|
| Layout | One issue per page (can be turned off). Page numbers. | Sheets: Issues (one row per issue), Comments (one row per comment), Attachments (one row per file). No merged cells. |
| Basic fields | Key, summary, type, status, priority, assignee, reporter, created, updated, due date, resolution, labels, components, fix versions, description | |
| Custom fields | Custom fields that have a value, shown as readable text: users, options, dates, SLAs, time tracking, linked issues and more. Internal system fields such as rank are skipped. | |
| Attachments | The list of file names, sizes, authors and dates. File contents are not embedded. | |
| Languages | Screen and file labels in English or Japanese, following the user's Jira language. Fonts for Japanese, Chinese, Korean, most European languages and emoji (black and white) are embedded. | |
Text is written as plain text cells (attachment sizes are numbers), so values starting with = are never run as formulas. Excel allows at most 32,767 characters per cell; longer values are shortened and marked.
Some fields are useful inside a team but awkward to share with a customer. They are listed but start unchecked; check them to include them:
Sentiment · SLA fields (for example Time to resolution) · Security level · Linked issues · Approvals · Request participants · Status category and its change date · Major incident · Responders
Other fields that name people, such as Approvers, stay checked. Always review the field list before sending a file outside your team.
By default the files leave out Jira Service Management internal comments and comments restricted to a role or group. The number of left-out comments is not printed. To include them, check Include internal and restricted comments; each comment is then tagged [Internal], [Public] or [Restricted: role or group name].
Jira does not accept a search without a condition. Add one, for example project = ABC.
The app already waits and retries a few times on its own. If you still see this message, wait a minute and try again, or narrow the search.
Ask a Jira admin to check the app under Manage apps.
Only fields with a value in at least one of the found issues are listed. Fields you do not have permission to see are not returned by Jira.
Email contact@gramshift.com. Please include what you searched for, what you expected and what happened (a screenshot helps). Please do not send exported files or confidential issue content unless we ask for it. We reply by email and aim to answer within 3 business days (Japan time, Monday to Friday).
project = ABC ORDER BY key）。条件の無い検索は Jira が受け付けません。社内コメント（JSM）と、役割やグループに閲覧を限ったコメントは、既定では含めません。1回に書き出せるのは1,000件までです。お問い合わせ: contact@gramshift.com