Troubleshooting Gliffy for JIRA
Click a heading to view details.

JIRA treats Gliffy diagrams as attachments to issues, so your diagram must be attached to a saved issue. Unfortunately, if you did not save and name the issue in JIRA where you started and saved the Gliffy diagram, the diagram has no where to attach to. This is unfortunately a limitation of how JIRA treats Gliffy diagrams.
You can search in JIRA for the name of the Gliffy diagram to try to retrieve it. But if the search results do not find the diagram, it may unfortunately be lost.
We always recommend first creating, naming, and saving the issue in JIRA so that if you encounter a web browser or connection issue and you need to quit, a draft of your diagram would still be attached to the JIRA issue.
If you have further questions, contact our support team (see Contacting support).

If you know that your JIRA has a license for the Gliffy plugin, but yet you cannot access Gliffy from your issues, verify that you have permissions to add and delete attachments to an issue. Access to the Gliffy for JIRA plugin is available only to users tho have permission to add and delete attachments to issues. Delete attachment permission is required by Gliffybecause JIRAdoes not support attachment versioning. When a Gliffy diagram is edited/saved, the attachment must be deleted and recreated by Gliffy, with all previous versions bundled inside of it.
For information about how to verify your permission in JIRA, see https://confluence.atlassian.com/display/JIRA/Configuring+File+Attachments. If you do not have these permissions, contact your JIRA administrator.
If you do have the proper permission but you still can't access Gliffy, contact our support team (see Contacting support).

When you import Visio diagrams in Gliffy
- Visio symbols that are not supported in Gliffy appear as a red box.
- You may notice minor differences between the symbol in Visio and how it looks in Gliffy. All Visio shapes are currently imported as images with the exception of some simple lines.
- The .vdx or .vsdx file must be exported directly from Visio.
- You cannot import read-only Visio files into Gliffy. You must save the Visio diagram without the read-only restriction.
- Blank pages do not import. Remove blank pages before you export from Visio.
- Importing multiple worksheets is not supported. Separate your tabs/worksheets and then import them individually.
- Importing binary Visio files (*.vsd) is not supported.
- Lines connected to some shapes may pop into a different position when the shape moves.
- You cannot adjust the line width, line color, fill color, gradient, or drop shadow of imported Visio diagrams.
- Rotated shapes may have jagged lines.
- Sometimes lines may import as shapes. When this happens, you cannot attach the imported line to another shape.
- Paragraph formatting or tab formatting for text is not supported.
- Only fonts available in Gliffy are supported. All other fonts default to Helvetica or Arial.
- Shapes with shadows or gradients may cause file to not import
Here is a list of issues that may affect an entire class of diagrams.
Diagram type | Issues |
---|---|
ERD |
ERDs in Visio rely heavily on text formatting that Gliffy does not support. We do not recommend importing ERD diagrams yet. Table text may not align correctly. Lines that have multiple text nodes attached (such as lines with cardinality text) import as an image. Not all arrow endings are supported. ERD-specific behaviors are not available in Gliffy |
Swimlanes | You cannot modify the swimlane count. |
UML |
Lines that have multiple text nodes attached (such as lines with cardinality text) import as an image. Shapes with multiple text areas (such as class or object UML shapes) do not stretch and behave like they do in Visio or Gliffy. Instead, they stretch uniformly. UML-specific behaviors are not available in Gliffy. |
Floorplan |
Dashed lines and pattern fills do not appear. Line thickness may be different. |
Sitemap | Embedded EMF files do not import and appear as red squares (which some of the site map shapes that ship with Visio are). |
Network | Embedded EMF files do not import and appear as as red squares (3rd party vendor specific stencils can have these). |
Images |
Only png, jpg, bmp, and gif files are supported. Other formats appear as red squares. Bmp files are converted to png. Any bmp files with transparency are imported as png files without transparency. |
User Interface |
Text that relies on tabs or margins for positioning may not align as expected. Microsoft icons may not render correctly if they are not a supported image type. |