JIRA upgraded

[Tony Atkins]

Hi, All:

I just reviewed the release notes for a bit and experimented on the
upgraded instance.  The biggest change is that the new WYSIWYG editor is
now enabled by default for comments, editing descriptions, et cetera.  As
we have had very serious concerns with the Confluence WYSIWYG editor, I
reviewed the new editor in some depth this morning.  In summary, there are
concerns, but they aren't as pressing.

First, like Confluence, all the previous wiki markup works.  For example,
if you type "*word*", "word" is evolved to appear in *bold* as you type.
The behavior of macros is a little different, typing "{code}" starts (and
ends) an empty code block.  In short, if you just go on about your business
and type wiki markup, the worst that happens is a kind of autocomplete.
That, and you'll have to either hit return twice or backspace to close out
a bulleted list.

Arrow key navigation seems pretty good.  Navigating between text, code
blocks, etc. can all be accomplished in WYSIWYG mode using the arrows
keys.  Tab navigation is more problematic.  Bulleted lists in the WYSIWYG
editor are a partial tab trap.  You can tab out of the first entry, but
tabbing is treated as "indent one level" from the second item on.
Shift+tab is always trapped within a bulleted list as "unindent one
level".  Thankfully, arrow keys can navigate in and out of bulleted lists.
Once you get back to non-list text, tabbing works as expected.  As
mentioned above, there are two ways to finish up a bulleted list with a
keyboard, backspace on the last line, or hitting enter on an empty list
item.

I didn't want to deface an active issue, so I didn't test inline images in
detail.  My strong suspicion is that those will be basically doorstops that
you can navigate past but not change in WYSIWYG mode.

This brings me to the most important point, which is that, unlike
Confluence, users can still "opt out" and use the previous text editor by
hitting the "Text" tab in the editor.  This seems to be something backed by
a cookie rather than a profile setting, so you may have to "opt out" once
per browser session.  If you do "opt out", you have the ability to edit
every type of content as pure text.  If that doesn't prove to be enough,
unlike Confluence, there is also still the option to disable the WYSIWYG
editor site-wide.

For now, I would suggest that we postpone updating issues.gpii.net to give
us a few weeks to try out the new editor.  That way we can decide whether
"opt out" is enough for us, or whether we want to have the editor disabled
on both from the start.

Given our very serious concerns with the Confluence editor, I would also
suggest that we start sharing the JIRA release notes at least a week before
an upgrade, as we want to avoid unknowingly going past the point where
users can "opt out".

Cheers,


Tony

On Thu, Mar 16, 2017 at 10:18 PM, Tirloni, Giovanni <gtirloni at ocadu.ca>
wrote:

> Hello,
>
>   JIRA was upgraded from 7.2.5 to 7.3.3
>
>   Release notes: https://confluence.atlassian.com/jirasoftware/jira-
> software-7-3-x-release-notes-861181590.html
>
> Regards,
> Giovanni
> _______________________________________________________
> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20170317/c21a467a/attachment.html>