Docs & support
After PDFPins is installed, a project administrator adds the plan. Your Jira permissions determine which issues you can see and edit.
1. Open PDFPins in Jira
In a Jira Software project, open PDFPins from the project’s app navigation. In Jira Service Management, use Queues → Apps → PDFPins with a licensed agent account.
2. Choose a suitable PDF
Open Getting started in the app to download the sample floor plan, or use your own drawing. The limit is 50 MiB and 200 pages per PDF. Use a flattened PDF without passwords, forms, embedded files, or scripts.
3. Add the plan
Choose an issue in the same Jira project to hold the PDF. Make sure your intended teammates can browse that issue. A project administrator selects Add plan, names the plan, and chooses an existing attachment or uploads one to the selected issue. Finish with Validate and add plan.
4. Link an issue to a location
Select Place pin, choose a point on the drawing, and select an issue in the same project or create one with Jira’s dialog. If the newly created issue is not returned, search for it explicitly. Cancelling creation does not save a pin.
Creating a pin requires Jira’s Create Issues permission. One issue can have one location per plan.
5. Review and update the location
Select a pin to inspect its Jira fields or open the issue. To move it, drag it or focus it and use the arrow keys. Moving and removing pins require the linked issue’s Edit Issues permission, subject to the administrator cleanup behavior for unavailable issues.
Use the issue’s Plan location panel to find or update its linked locations. Return to the plan or reload after editing Jira to refresh the displayed fields.
6. Filter and export
Filter by status, priority, assignee, or due date to focus on the work for your walkthrough. On desktop or tablet, select Export PDF to download a marked snapshot with numbered pins and an issue legend.
Exports are produced locally in your browser and may contain issue information you can access. Share them according to your organization’s rules. They do not update after download.
When a drawing changes
Add a revised PDF as a new plan. Reconnecting a missing attachment requires an exact copy of the original PDF so saved locations keep their meaning.
Common questions
Why is Add plan missing?
Only a project administrator can manage the plan library. Ask your project administrator to add the plan. If the app is read-only, a site administrator may also need to check the PDFPins subscription.
Why can’t a teammate open the plan?
Check Browse access to the project and the issue holding the PDF, including any issue-security restrictions. Access to a project alone does not necessarily grant access to that attachment’s issue.
Why can’t I place or move a pin?
Check the subscription, internet connection, Jira Create/Edit Issues permissions, and whether the plan is active. A project administrator can restore an archived plan.
Why won’t my PDF load?
Confirm the attachment still exists and you can access its Jira issue. Check that the PDF meets the size, page, and supported-content limits. A viewing error alone does not mean the shared plan is unavailable. Ask an administrator before changing its availability.
What happens when the subscription is inactive?
Adding and editing stop. Viewing, export, and authorized cleanup remain available. Ask your site administrator to check the app subscription in Atlassian app management.
Does deleting a plan delete its Jira issues?
No. It removes PDFPins metadata and pin locations. Jira issues and attachments remain.
Contact support
Include the approximate time and time zone, browser and version, action attempted, and sanitized error message. Mention whether a reload or retry changed the result. Use fictional data for a reproduction where possible.
Please do not send passwords, API tokens, session data, private Jira links, customer screenshots, exported reports, or PDF attachments.
PDFPins Support — support@pdfpins.com
Security
Access follows Jira
The app derives account and project scope from Forge’s invocation context. It rechecks Jira access as the current user and scopes plan, pin, issue, and attachment lookups to the current project.
Project administration is required to manage plans. Pin creation requires Create Issues permission; moving or removing a pin requires Edit Issues permission for its linked issue, with a documented administrator cleanup path for unavailable issues.
A limited app data footprint
PDFPins stores references, plan metadata, and pin locations in Forge. PDF bytes, attachment URLs, and live issue fields are not persisted in its storage. The app does not send Jira content to a vendor remote.
PDF handling
The app checks PDF size, format, page count, and unsupported content before use. Password-protected files, forms/XFA, embedded files, and active content are unsupported. These checks are not a general-purpose malware scanner; use files appropriate for your organization’s environment.
Report a vulnerability privately
Include a concise description, expected and observed behavior, and reproduction steps using synthetic data where possible. Do not send passwords, tokens, private PDFs, customer issue content, or screenshots containing confidential information. Do not publish exploit details before reporting them privately. Email the address below with “Security” in the subject.
PDFPins Support — support@pdfpins.com