Overall the migration looks pretty good I would agree. I was impressed to see things like dependencies come through pretty cleanly.
The one problem I have that I assume is related to this formatting is that it seems like line wrapping does not happen as it normally would. So descriptions etc seem like a series of fixed-width monospaced lines. A lot of the Jira UI seems to expect it to be a block of text that it would line wrap as needed. Or at least I assume that is what it would look like. So many of the normal screens you cannot really read a lot of the text without going into full screen. That said, I cannot remember the last time I even went into IssueZilla. So I cannot say this will impact me at all. Whatever you guys decide is OK with me. Mark On Wed, Sep 16, 2015 at 9:10 AM, Greg Stein <gst...@gmail.com> wrote: > Well, the noformat in the test import looks just fine. It works, may as > well leave that. ... But end the work there. I'm with Mark: having the > issues in JIRA is *way* more important than further refinements and the > time involved. > > On Wed, Sep 16, 2015 at 8:00 AM, Mark Phippard <markp...@gmail.com> wrote: > >> If what Johan says is all true (which I assume it is) then why not just >> do a straight-up migration of issues and let things be proportional? You >> could then manually correct the parts of descriptions or comments that >> would be better be formatted differently ... but only if someone cares >> enough. >> >> If it is an old closed issue, who would even care? >> >> Anyway, it just seems like new issues moving forward will be proportional >> font except where people choose to change format, so why not do same for >> history? Especially given that it seems easier. >> >> Mark >> >> >> On Wed, Sep 16, 2015 at 6:07 AM, Johan Corveleyn <jcor...@gmail.com> >> wrote: >> >>> On Wed, Sep 16, 2015 at 11:59 AM, Ivan Zhakov <i...@visualsvn.com> >>> wrote: >>> > On 16 September 2015 at 11:32, Stefan Hett <ste...@egosoft.com> wrote: >>> >> Hi, >>> >>>> >>> >>>> 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. >>> >> >>> >> Unfortunately not at all, otherwise I would have offered to do so. >>> >> While I do have some decent knowledge of Java due to my studies, I >>> haven't >>> >> been coding in Java for several years now and don't even have a >>> development >>> >> environment set-up for that. >>> >> >>> > I also don't have Java environment, while I developed several plugins >>> > more then 10 years ago. >>> > Link to the Atlassian tutorial if ever want to learn it: >>> > >>> https://developer.atlassian.com/docs/getting-started/set-up-the-atlassian-plugin-sdk-and-build-a-project >>> > >>> >>> I think we're almost there: I don't think we need a custom renderer or >>> plugin. Apparently, we can get what we want by enclosing everything >>> coming from bugzilla within: {noformat:nopanel=true} >>> >>> That way, we still have the option of using the normal rendering for >>> new issues (or even editing old issues to move "nicer parts" out of >>> the noformat block), and only put inside a noformat block the things >>> which really need to be monospaced. >>> >>> See here for an example: >>> >>> https://issues.apache.org/jira/browse/TST-210?focusedCommentId=14747248&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14747248 >>> >>> >>> >>> -- >>> Johan >>> >> >> >> >> -- >> Thanks >> >> Mark Phippard >> http://markphip.blogspot.com/ >> > > -- Thanks Mark Phippard http://markphip.blogspot.com/
