[WG: Sakai QA] [DG: User Experience] [Building Sakai] Jira upgrade: 3.13.2 -> 4.1.2

[Anthony Whyte]

Yes, the "washed-out" complaint regarding, in particular, the view issue page appears widespread.  See

http://jira.atlassian.com/browse/JRA-20669

You can compare the new look against the old here:

Jira 3.13.2: http://jira.sakaiproject.org/browse/SAK-15817
Jira 4.1.2: http://72.249.101.17:8080/browse/SAK-15817

The new look lacks the clear delineations that once existed that helped the eye navigate between details, description, etc.   The issue operations that appeared on the left have migrated to a horizontal operations bar.  There are other UI changes that will require getting used to but I think delaying the upgrade while we wait for Atlassian to tweek the GUI is not in our interest.

Personally, I'd like to take advantage of improvements to "bulk move" operations that now include the mapping of old project values for components and versions to new values, a feature lacking in Jira 3 that made moving issues between projects (such as Sakai -> Samigo) problematic.  Other new features and fixes are listed in the 4.1 release notes:

http://confluence.atlassian.com/display/JIRA/JIRA+4.1+Release+Notes

In addition, I have added the charting plugin to the test instance per Alan Mark's request and am also working to add the Greenhopper agile project management plugin per Beth Kirschner's request.


Cheers,

Anth



On Sep 17, 2010, at 5:53 AM, Adam Marshall wrote:

> the main problems for me are:
>  
>  - issue page. this has been radically changed and it is now very hard to spot things on a page. The overall look is very pale (washed-out) which decreases usability / freadability. Also thre's a very annoying scrolling feature which makes it hard to go back to the top of the page
> - lack of 'filters' drop down on every page. One of the miost useful features was the 'filters' drop down list. This has been changed so you now only get a handful of filters in the list - if you have more than 10 filters you have to use 2 clicks to jump to a page.
> - many of the links on the project home page have either vanished or been hiddens somewhere on the page - after 3 mionths I still havent found some of the links I used to use on a daily basis
>  
> I think the overriding issue is tha te UI has changed so much that one has to learn how to use the system all over again.. The best bet is to try out your regular workflow and see how hard navigation appears to be.
>  
> adam
>  
> From: Alan Berg [mailto:qa.director.sakai at gmail.com] 
> Sent: 17 September 2010 10:04
> To: Adam Marshall
> Cc: Anthony Whyte; Developers Sakai-Dev; Nakamura List; sakai-ux at collab.sakaiproject.org; Sakai QA; Sakai Development UI
> Subject: Re: [DG: User Experience] [Building Sakai] Jira upgrade: 3.13.2 -> 4.1.2
>  
> Hi Adam,
> 
> Can you please be more specific. A bullet list of minus points would be helpful for discussion. Without any real face time Jira 4 looks on the surface better.
> 
> Alan B.
> 
> On Fri, Sep 17, 2010 at 10:56 AM, Adam Marshall <adam.marshall at oucs.ox.ac.uk> wrote:
> We moved to jira 4 and I wish we hadnt.
>  
> In my opinion the interface is vastly inferior compared to Jira 3 - I would think long and hard before moving. Atlassian are working on a new UI which answers many of the biggest complaints and it may be worth waiting until that is released before upgrading.
>  
> so that's a -1 from me.
>  
> adam
>  
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20100917/51f83683/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3829 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20100917/51f83683/attachment.bin