HTML tags when exporting to Excel

I have installed the Last Comment pluguin and works fine, but, when exporting to Excel, it shows the <p></p> HTML tags surrounding the comment.

Is it possible to suppress those tags?

5 answers

1 accepted

2 votes

would anyone like to close this thread now? this problem has been resolved since early march.

Thanks

-wc

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thanks for coming back and marking the question answered - this one was a pain to get resolved, took time and we pissed off a few people but in the end the Addon is much more solid and well managed. -wc

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

2 votes

It would depend on what version of the plugin you are using. The later versions have the option to render the last comment excerpt using the plain text renderer which strips out the HTML tags.

We have a request to enhance the plugin such that it always uses the plain text renderer when ...er... rendering itself for excel exports. You can vote on the issue here: https://capitalplugins.atlassian.net/browse/LCCF-27

Thanks,

-wc

Capital City Consultants

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

2 votes

Ok - we will have a release out this week that provides the ability to specify the renderer when exporting to excel. Selecting 'Plain Text' for the export will remove all HTML tags from the last comment field (as long as they weren't explicitly added when the comment was made - i.e. if you enter <b> my comment </b> as a comment then the tags won't get removed)

-wc

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

well, the new code worked fine but the old code just didn't like it much and the whole thing causes your JIRA server to be unable to create new issues....so, we've gone back to our Quality department and done a bit of rearrangement which should result in a working version out next week.