Print Issues-->Card designer-->Print Preview does NOT match what actually prints out.

[Charles Sager]

In all of our stories, we have a table inserted at the top of the description field as so:

===============

===================

One negative is that I can't adjust the column widths as I would expect to in any word processor, or spreadsheet.  But, I have found that if I just add some text such as "--------->" jira will auto adjust the columns somewhat.

My problem comes into play when I want to print a card for our physical Kanban board.  I right click the 3 dots upper right of page, choose "print issue", I design a card in the card designer, then make sure it looks good in the "Print Preview" tab.  But when I print the card, the text that I saw aligned the way I wanted in "Print Preview" is now wrapped in the cell.  In other words "Print Preview"  rarely matches what actually gets printed on a physical sheet of paper.  "Start Date ---------->" prints out as 2 lines as so:

Start Date

---------->

instead of how it displays in the "Print Preview"

Can these bugs be fixed in jira?

[Daniel Eads · Accepted solution]

Hi Charles!

Looks like this functionality is provided via the Agile Cards - Print Issues from Jira app. I've added a tag to this question so that Spartez, the app vendor, has a better chance of seeing the question.

If you don't get an answer shortly, you can also ask a question directly with Spartez on their Service Desk. Providing any answer you get from a private support request back here on Community helps everyone out, if you end up needing to do that!

Cheers,
Daniel

[Charles Sager]

Ok, I filed a bug with Spartez, reference is SUP-7134.  I referenced the jira bug described here on this page.  We'll see if they can provide a fix.

[Charles Sager]

Ok, so this was isolated to being a problem only in Firefox (other browsers?).  Using Chrome, print preview matches what is printed out, so using the Chrome browser in the card designer, and for print preview is the work-around.  Spartez say they will keep the bug with Firefox open but do not have a timeline for a fix.