|
[
Permlink
| « Hide
]
Neal Applebaum added a comment - 16/Feb/05 09:39 AM
this should be Minor, not Major.. sorry.
Neal,
Is the intention here to be able to print just the issue's fields, without comments? – The issue is to be able to print the issue (i.e. hard copy to a printer) with one clickable link. I would expect it to print an issue to match the format of the "Full Content" view - i.e. the same layout and presumably same code base to generate both. It prints comments.
Ideally, pressing "Print" would also present an option to include Comments/Change History/All like viewing on line does. JIRA issues are displayed as regular HTML pages, for which it is the browser which does the printing (and has the print button). So we can't have a 'Print' link in the menu. However we can alter what's displayed so that when the user clicks the browser Print button, only desired content is displayed.
If it isn't possible to get JIRA displaying exactly the subset of information that you're after, let us know and we can investigate making it possible. .. understood. Many web pages have a "Print" button which offers a printer friendly version of an issue which is then printable via the browser's print button. Maybe there could be a similar functionality - i.e. it would be a link (maybe called 'Print View') that causes a nicely formatted version of the issue ready for printing. I know your standard is to not launch new windows, so the user would have to remember to open the 'Print view' in a new window and then press Print. It's a lot faster than doing a search to narrow the issue down, then pressing 'full content'.
Neal,
We are planning to provide an MS Word export of an issue. This wil allow you to export an issue and comments to MS Word and then pribt from there. Word has very powerful printing functionality and we would like to leverage it. With this solution, printing would not be done with one click, however. Is being able to print with one click exteremely important? Will the MS Word export work for you? Thanks, Export to Word would be a fine enhancement (for me anyway).
I agree with Neal. Additionally you can email the word file which will be handy.
So, will you have an option whether to include Comments/Change History/All like viewing on line does before exporting the issue?
On the first go it will be just comments.
PDF might be another way to export an issue.
Also, seems like this issue should be renamed if it really is about providing an export to MS Word format. Serge,
PDF is definitely a good option as well. Ideally we would make the view types a plugin so people can create their own views for an issue. This would hopefully suit most people. Cheers, Guys,
This issue seems to have meandered somewhat. Can we close this as being incorporated by Cheers, Mark C Well, preferably, I'd want a Print (rather than Export) operation - for training/usability reasons - , but I'll take whatever you serve up for now, and log additional improvement requests as necessary.
Neal,
I guess the "workaround" for now is to actually print the issue from the browser? For example, if you just print this issue this will look like this PDF I think what we need added to this issue are more specific requirements of what is really required here. (what needs to be displayed, how does it have to look etc) In any case, we'll push the proper fixes for this to 3.6 Cheers Mark C Yeah - the problem is that the browser output isn't that pretty and page breaks are messy.
Having the print icon simply format the page the exact same as does selecting the Full Content view is what is desired. Users simply want to print out a full issue while killing as few trees as possible and in the *shortest amount of time as possible. An export to word is not a solution to this problem, as Mark admits, it is just more hoops the user has to jump through to get a simple hard copy.
Suppose you are late for a meeting with the big brass. An issue is causing customers to hammer you daily and it's affecting your bottom line. You need to pass around hard copies of the issue for discussion but to get a decently formatted hard copy you have to perform 6 operations just to get to where you can print to a printer. Fancy is only fun if it is efficient. I think Kevin and I are on the same wavelength. JIRA is so intuitive that I only spend about 2-3 minutes training new users. And after that I hardly ever get asked for more info unless a PM type needs to produce an Excel output. I didn't even notice that little print icon when I created this issue almost a year ago. When I was looking at a competitor's product (Visual Intercept) they had buttons to email an issue or print an issue and that's where my request(s) came from. I liked that intuitive interface. One step and it created an email with a pretty version of the issue in HTML format, or on the printer. I tried, in vain, to get the hr.gif diamond separator to translate to a page break from the browser too.
Thanks for the feedback folks, really appreciate it.
I've fixed this for 3.5 and created an issue for it at I'm pretty sure that this is fixed by
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Resolved
Minor
would like 'Print this issue' functionality
