Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-31132

EAP Feedback - JIRA 6.0 Atlassian Design Guideline Rollout

    • Icon: Suggestion Suggestion
    • Resolution: Done
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Hi everyone,

      Welcome to the JIRA 6.0 Early Access Program (EAP)!
      Thanks for trying out our early look at our next release. You can download the latest EAP release (milestone build, beta or release candidate) here.

      We have an existing issue (JRA-30983) to capture general feedback. This issue is the place to provide your thoughts on the new JIRA interface design that can be seen in JIRA 6.0 EAP 2 and all future EAP releases.

      We really appreciate you taking the time to provide us any feedback on the contents of the EAP.
      Simply comment below for any comments you may have.

      Cheers,
      Bryan, Roy, Mairead, and Josh
      JIRA Product Management

        1. JIRA 6.0-m04-modified.png
          JIRA 6.0-m04-modified.png
          337 kB
        2. JIRA 6.0-m04-orig.png
          JIRA 6.0-m04-orig.png
          341 kB
        3. JIRA view issue page 6.0-m04 modified.png
          JIRA view issue page 6.0-m04 modified.png
          287 kB
        4. JIRA view issue page 6.0-m04 orig.png
          JIRA view issue page 6.0-m04 orig.png
          256 kB
        5. JIRA view issue page 6.0-m04 modified with marker.png
          JIRA view issue page 6.0-m04 modified with marker.png
          292 kB
        6. Login gadget broken.png
          Login gadget broken.png
          193 kB
        7. Tempo Admin Navigation.png
          Tempo Admin Navigation.png
          98 kB

            [JRASERVER-31132] EAP Feedback - JIRA 6.0 Atlassian Design Guideline Rollout

            Holger Schimanski added a comment - - edited
            • I noticed, that in blue button and in Issues menu you use "Create issue" instead of "Create Issue". On other place you use chapital letter like "Search for Issues".
            • "Sign up" link in login gadget is not translated to german.
            • The link you get proposed to switch to mobile version of JIRA when using e.g. iPhone redirects to login screen (at jira.atlassian.com). Shouldn't the mobile version also be usable by unlogged user?

            Holger Schimanski added a comment - - edited I noticed, that in blue button and in Issues menu you use "Create issue" instead of "Create Issue". On other place you use chapital letter like "Search for Issues". "Sign up" link in login gadget is not translated to german. The link you get proposed to switch to mobile version of JIRA when using e.g. iPhone redirects to login screen (at jira.atlassian.com). Shouldn't the mobile version also be usable by unlogged user?

            Holger Schimanski added a comment - - edited

            Did had a look at 6.0-rc1 today. I really like view issue page now! Also Administration menu and tab layout looks nice. Thank's also for bringing back Admin search box.

            The switch between browse project and admin project is nice, but I would prefere buttons, because the tabs are waisting too much horizontal space. Actually I would merge admin versions with browse versions into one versions tab and same for versions. Then for most of the users resp. project admins there is no need to switch of view the project admin tab anyhow.

            What is confusing is the head line "concept" when switching through the vertical tabs in Administration and Project Administration.

            • When clicking on "System Info" the tab head line is "System Info". Fine!
            • Selection "Versions" tab in browse project, the tab head line is "Versions". Good!
            • Selecting "Versions" in project admin, the head line is "Versions" plus version logo. Okay!
            • If I go to "Issue Types" the header is "Issue Types Default Issue Type Scheme". But Default Issue Type Scheme is the sected value. That Default Issue Type Scheme is not a tab head line, but a selectable value is not resprected in its UI presentation. An untrained user don't really has a clue, that this is a parameter of the project, which can be changed.
            • Same for Screens, Fields, Permissions etc.
            • Click "Find new addons" than head line is "Atlassian Marketplace for JIRA".
            • "Application Links" is "Configure Application Links"
            • "Issue Collectors" is "All Issue Collectors"
            • "User Preferences" is "User Default Settings"
            • "Statuses" is "View Statuses"
            • etc.

            Holger Schimanski added a comment - - edited Did had a look at 6.0-rc1 today. I really like view issue page now! Also Administration menu and tab layout looks nice. Thank's also for bringing back Admin search box. The switch between browse project and admin project is nice, but I would prefere buttons, because the tabs are waisting too much horizontal space. Actually I would merge admin versions with browse versions into one versions tab and same for versions. Then for most of the users resp. project admins there is no need to switch of view the project admin tab anyhow. What is confusing is the head line "concept" when switching through the vertical tabs in Administration and Project Administration. When clicking on "System Info" the tab head line is "System Info". Fine! Selection "Versions" tab in browse project, the tab head line is "Versions". Good! Selecting "Versions" in project admin, the head line is "Versions" plus version logo. Okay! If I go to "Issue Types" the header is "Issue Types Default Issue Type Scheme". But Default Issue Type Scheme is the sected value. That Default Issue Type Scheme is not a tab head line, but a selectable value is not resprected in its UI presentation. An untrained user don't really has a clue, that this is a parameter of the project, which can be changed. Same for Screens, Fields, Permissions etc. Click "Find new addons" than head line is "Atlassian Marketplace for JIRA". "Application Links" is "Configure Application Links" "Issue Collectors" is "All Issue Collectors" "User Preferences" is "User Default Settings" "Statuses" is "View Statuses" etc.

            moxin added a comment -

            i was thinking of fixing it myself by using a webresource plugin. how can you run an AJS jquery function to load on Dashboard page? i have tried using context but to no avail.
            here is the question i posted on answers.atlassian.com
            https://answers.atlassian.com/questions/150185/run-an-ajs-jquery-function-on-jira-dashboard

            moxin added a comment - i was thinking of fixing it myself by using a webresource plugin. how can you run an AJS jquery function to load on Dashboard page? i have tried using context but to no avail. here is the question i posted on answers.atlassian.com https://answers.atlassian.com/questions/150185/run-an-ajs-jquery-function-on-jira-dashboard

            My bad Paul, you are correct that it indeed shows the Add-ons admin section.

            However, it would be feasible if the admin would see only links to Tempo pages, not Fisheye or other products, when he navigates to the Tempo Admin section. Is this something we can do by changing the web-fragments/decorator configuration?

            Thanks,
            Viðar

            Viðar Svansson [Tempo] added a comment - My bad Paul, you are correct that it indeed shows the Add-ons admin section. However, it would be feasible if the admin would see only links to Tempo pages, not Fisheye or other products, when he navigates to the Tempo Admin section. Is this something we can do by changing the web-fragments/decorator configuration? Thanks, Viðar

            sladey added a comment -

            pjesi the left hand menu does not represent the "core" admin navigation. This is the subset of the navigation under the "Add-ons" top-level admin section.

            sladey added a comment - pjesi the left hand menu does not represent the "core" admin navigation. This is the subset of the navigation under the "Add-ons" top-level admin section.

            It is not very useful to have the core Admin navigation on the left when inside the Tempo Administration section. It was much better in JIRA 5 where the left navigation only contained links from the Tempo admin section.

            I recall that we had to support two different admin navigation structures when JRIA 4.4 was released. Is this a similar case that we are unaware of?

            Viðar Svansson [Tempo] added a comment - It is not very useful to have the core Admin navigation on the left when inside the Tempo Administration section. It was much better in JIRA 5 where the left navigation only contained links from the Tempo admin section. I recall that we had to support two different admin navigation structures when JRIA 4.4 was released. Is this a similar case that we are unaware of?

            sladey added a comment -

            mohsin213jc we are on it.

            sladey added a comment - mohsin213jc we are on it.

            moxin added a comment -

            the font on gadget title is too big
            http://oi48.tinypic.com/x5589d.jpg

            moxin added a comment - the font on gadget title is too big http://oi48.tinypic.com/x5589d.jpg

            Not sure whether round project avatars will survive (I hope not), but in case of that incident - you should indicate that functionality also in project avatar setting dialog - and let user trim it in circle.

            Jozef Kotlár added a comment - Not sure whether round project avatars will survive (I hope not), but in case of that incident - you should indicate that functionality also in project avatar setting dialog - and let user trim it in circle.

            sladey added a comment - - edited

            holger.schimanski@bayerbbs.com you may be pleasantly surprised with 6.0-m9 or 6.0-m10 - we love your thinking here.

            sladey added a comment - - edited holger.schimanski@bayerbbs.com you may be pleasantly surprised with 6.0-m9 or 6.0-m10 - we love your thinking here.

              Unassigned Unassigned
              pslade@atlassian.com sladey
              Votes:
              0 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: