FishEye UI needs a major overhaul after upgrading from 1.5 -> 2.1.4

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Answered
    • None
    • Component/s: User interface
    • None
    • Environment:
      Atlassian FishEye repository viewer (Version:2.1.4 Build:build-460 2010-01-26)

      We've just upgraded from FishEye 1.5 to 2.1.4 - looking forward to the newly improved GUI - at least, that is what we thought.

      I'm not sure what happened here, but it is extremely difficult to navigate or get an overview of the information now - the output format takes up a lot more room than in the previous version and it feels like we've lost control unfortunately.

      It seems that Jira/Confluence (which has a lot more of functionality) is significantly better structured and much easier to use than FishEye is now in the new version.

      I really think the UI needs to be rethought significantly from scratch - I could try to come with individual cases for improvement, but I don't think that is a fruitful way forward - if you'd like a sounding board, I'd be happy to do it.

      Just some short comments, not complete:

      • One wants to follow commits and statistics for just a few releases (two, max three for us), one one or perhaps two screens (similar to Jira dashboards)
      • Using FishEye as the "heart beat" of development by looking at the commits

      I really love the functionality and we are very happy customers for several of your other products - it just seems that FishEye really took a step backward in usability here - we know you can do a lot better! We've had multiple users complaining about it (not that it is different, we all hoped for that - just that it is unfortunately not even as good as the previous version)

            Assignee:
            Unassigned
            Reporter:
            Joakim Hassila
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: