[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Migrating Subversion issues to ...

From: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Wed, 16 Sep 2015 10:53:44 +0200

On 16 September 2015 at 02:43, Stefan <luke1410_at_posteo.de> wrote:
> Hi,
>> [...]
>> As to "format all descriptions as <pre>" in jira: honestly, it feels
>> like a round peg in a square hole. Jira is designed around ajax and and
>> html; I'd be concerned that future releases of jira might break the
>> renderer plugin Ivan is planning to write — and if that happens, infra
>> might simply disable the plugin until we fix it, since we'd be the only
>> project affected.
>> [...]
> I needed to be convinced by brane and jamessan on IRC that it's better to
> send this reply to the list directly rather than by IRC. ;-)
> Don't take this reply the wrong way please. I'm not trying to talk the one
> person who speaks up in favor for bugzilla into anything.
> Just wanted to point out that you (i.e. the subversion developers) are
> certainly not the first ones to bring-up the limitations of monospace
> support in JIRA. See: https://jira.atlassian.com/browse/JRA-37076 (issue
> regarding the added scrollbars when using monospace).
> Since the issue is on record for Atlassian, there's actually some chance
> that it gets resolved at some point (the more votes it gets, the more likely
> it will be taken care of at one point).
> On the other side I don't want to hide anything, so there are also the known
> issues with monospace in JIRA atm:
> https://jira.atlassian.com/browse/JRA-39011?jql=project%20%3D%20JRA%20AND%20status%20%3D%20Open%20AND%20text%20~%20%22monospace%22
We have to use {normat} tag instead of {monospaced} since we need to
preserve spaces to keep ascii graphics, etc.

> Speaking about Ivan's suggested monospace-renderer-plugin and the concern
> that it might break with a future version of JIRA: My experience with JIRA
> (which dates back to around 2005 I guess) is that Atlassian is quite
> reluctant with introducing changes which break plugins. So it's quite rare
> that that a plugin which works in 6.0 breaks during the 6.x releases. Things
> are slightly different when the major version numbers change, but then this
> only happens every 2 years or so. Hence the maintenance work for such a
> plugin should be considered quite low in the general case.
> On the other side Atlassian requires plugin developers to maintain and test
> their plugins on a regular basis (so they are still ensured to be compatible
> with later versions).
> If that's some concern and there is some help wanted/needed, I'd be willing
> to offer Ivan a hand with the maintenance work on his plugin (if that would
> help). As a test environment I'd provide my own JIRA instance, so that would
> not add much workload to me.
Thanks for offering help, but I already have test JIRA instance at my
office that I used for Serf project issues migration.

Btw do you have any experience in writing JIRA plugins? Writing
monospaced (preformated) text render would be big help.

Ivan Zhakov
Received on 2015-09-16 10:54:18 CEST

This is an archived mail posted to the Subversion Dev mailing list.