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.

          Form Name

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

            NickN added a comment -

            ncarbonneau, it was rolled out on Monday so should be available. Can you let me know your onDemand instance details and I'll check.

            NickN added a comment - ncarbonneau , it was rolled out on Monday so should be available. Can you let me know your onDemand instance details and I'll check.

            Hi Nick,

            I see this issue as resolved, but I cannot see any change in On-Demand, I still only see the lozenge, no text.

            Thanks, Normand

            Normand Carbonneau added a comment - Hi Nick, I see this issue as resolved, but I cannot see any change in On-Demand, I still only see the lozenge, no text. Thanks, Normand

            NickN added a comment -

            The updated lozenges (in subtle style) are now available in onDemand. Thanks for all the feedback.
            Cheers,
            Nick
            JIRA Product Management

            NickN added a comment - The updated lozenges (in subtle style) are now available in onDemand. Thanks for all the feedback. Cheers, Nick JIRA Product Management

            NickN added a comment -

            That's the best estimate I have simon3. Keep an eye on the https://confluence.atlassian.com/display/AOD/What%27s+New page for announcements.

            Cheers,
            Nick

            NickN added a comment - That's the best estimate I have simon3 . Keep an eye on the https://confluence.atlassian.com/display/AOD/What%27s+New page for announcements. Cheers, Nick

            On which date? "Mid January" is a touch on the vague side.

            Simon Lambert added a comment - On which date? "Mid January" is a touch on the vague side.

            NickN added a comment -

            Hi simon3, this particular change is scheduled for release in mid-January.

            NickN added a comment - Hi simon3 , this particular change is scheduled for release in mid-January.

            +1

            MattS added a comment -

            Nick, that's good news, thanks for the info

            MattS added a comment - Nick, that's good news, thanks for the info

            Hi Nick, when is 6.2 scheduled to be deployed for On Demand customers?

            Simon Lambert added a comment - Hi Nick, when is 6.2 scheduled to be deployed for On Demand customers?

            NickN added a comment -

            Hi Everyone, thanks for the feedback on the new designs. We realise this is a large change, and that's why wanted to share the details and get feedback. Based on your comments for the compact design, we're going to change this to include text. The examples and context you've all provided have really helped in informing this decision. This change will be made in time for the 6.2 release.

            Cheers,
            Nick
            JIRA Senior Product Manager

            NickN added a comment - Hi Everyone, thanks for the feedback on the new designs. We realise this is a large change, and that's why wanted to share the details and get feedback. Based on your comments for the compact design, we're going to change this to include text. The examples and context you've all provided have really helped in informing this decision. This change will be made in time for the 6.2 release. Cheers, Nick JIRA Senior Product Manager

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

                Created:
                Updated:
                Resolved: