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

      With the new ADG work for JIRA 6.2 (http://blogs.atlassian.com/2013/12/new-issue-status-jira-adg-lozenge) the name of the status of each subtask has been replaced by a colored lozenge. Hovering over the lozenge shows the status name.

      This is a problem because a user can no longer distinguish between two subtasks with different statuses but the same category when viewing the list of subtasks in the parent task. They now have to hover over each subtask's lozenge. With more than a couple of subtasks this is unusable.

      Also, https://developer.atlassian.com/design/latest/colors.html says "Don't rely on color alone to convey state or meaning" and this change clearly breaks that.

            [JRASERVER-36153] Can't distinguish sub-task or link statuses

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.02
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2834164 ] New: JAC Bug Workflow v3 [ 2924384 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2557531 ] New: JAC Bug Workflow v2 [ 2834164 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1541078 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2557531 ]
            jonah (Inactive) made changes -
            Description Original: With the new ADG work for JIRA 6.2 (http://blogs.atlassian.com/2013/12/new-issue-status-jira-adg-lozenge) the name of the status of each subtask has been replaced by a colored lozenge. Hovering over the lozenge shows the status name.

            This is a problem because a user can no longer distinguish between two subtasks with different statuses but the same category when viewing the list of subtasks in the parent task. They now have to hover over each subtask's lozenge. With more than a couple of subtasks this is unusable.

            Also, https://developer.atlassian.com/design/latest/colors.html says "Don't rely on color alone to convey state or meaning" and this change clearly breaks that.

             
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRACLOUD-36153].
              {panel}

            With the new ADG work for JIRA 6.2 (http://blogs.atlassian.com/2013/12/new-issue-status-jira-adg-lozenge) the name of the status of each subtask has been replaced by a colored lozenge. Hovering over the lozenge shows the status name.

            This is a problem because a user can no longer distinguish between two subtasks with different statuses but the same category when viewing the list of subtasks in the parent task. They now have to hover over each subtask's lozenge. With more than a couple of subtasks this is unusable.

            Also, https://developer.atlassian.com/design/latest/colors.html says "Don't rely on color alone to convey state or meaning" and this change clearly breaks that.

             
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-36153 [ JRACLOUD-36153 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-cloud affects-server
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 677279 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1541078 ]
            Oswaldo Hernandez (Inactive) made changes -
            Affects Version/s New: 6.2 [ 37820 ]
            Affects Version/s Original: 6.2-EAP [ 37295 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v5 [ 642767 ] New: JIRA Bug Workflow w Kanban v6 [ 677279 ]

              Unassigned Unassigned
              73d805a2526b MattS
              Affected customers:
              14 This affects my team
              Watchers:
              27 Start watching this issue

                Created:
                Updated:
                Resolved: