Starting with JIRA 5, when you are in issue edit mode, and have an issue type with multiple tabs, it is no longer possible to print the issue and get a printout that reflects what the user sees on the screen. This is because apparently the code that renders to a printer does not treat the field layout onto tabs in the same way as the renderer to the browser screen. See attached examples.
My organization really depended on being able to print the different tabs in order to get feedback from users, do training, and print documentation. The current ability to print pages is useless if the pages have tabs, because the printed page has no resemblance to the tabbed interface the user actually sees during data entry.
Screen prints are a possible solution until you get too many fields and the form becomes too long for a single screen, at which point it becomes a lot of work to stich together multiple screen prints.
I am currently working on SQL queries to reproduce the capability that used to exist in JIRA 4 and prior. I wonder how others are dealing with this loss of functionality? Is there a good workaround that I am overlooking?
Well, it's not a "loss of functionality", browsers have always worked like that and Jira has had tabs and long screens for many years. I'm afraid the short answer is that you'll need to choose between having the tabs or having to do multiple prints.
Sorry Nic, but, it did work much better in JIRA 4 and earlier. I'll attach "screenshot-1" which was captured from a JIRA 4 instance. Sure the printout ran for multiple pages, and was a bit messy, but, when you asked your browser to pint the current page, and you were on a JIRA edit-issue tab, it would only print the fields that were on that tab, and it would print them in the order that they appear on the screen. That was exactly what I would have expected my browser to do, and it met a number of needs.
The way it works in JIRA 5 (print page pays no attention to tabs) is much less useful because if you are using tabs on the screen you would expect the printout to follow suite.
Thanks to support staff this has been entered as a development issue at:
Prior to JIRA 5, it was possible to print the data entry "tabs" of a JIRA project and have printed pages that looked very much like the data entry "tabs" do on the screen.
With the release of JIRA 5 Atlassian "broke" this feature. JIRA 5 and subsequent releases print all of a screen's fields without respect to which "tab" the field appears on. With relatively small (few fields) tabs, you can of course use screen capture and print the image... but, with tabs that have many fields and require vertical scrolling, printing screen capture images is at best a messy solution.
Since we know that the vendor already owns code that prints these the way we want them printed... it seems like it should only be a matter of getting some votes for the issue to get that code put back. (Perhaps though some slightly different button or drop-down menu so we don't break the new behavior!)
Please consider voting for issue JRA-28071.
Use the PDF View Plugin to print your issues, and you will never see this problem again. Plus you'll have much better quality printout than printing the browser's content.
This add-on does not rely on the browser and its rendering and page breaking capabilities, but transforms the underlying data (tabs and custom fields) to printable documents.
See some samples in the top part of this page.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs