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

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

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.

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

+1

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

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

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

One question here: In order to have the status corresponding to the Lozenge color, we need to hover over it. What happens on the mobile versions of JIRA? I did not try it, but probably there is no hovering, which may be inconsistent.

I submit a PDF (https://jira.atlassian.com/secure/attachment/106249/lecture_icons.pdf) of the customized status icons we had devised for our workflow/statuses. We just devised these and implemented them 2 weeks ago, just before the new lozenges were pushed out.... Argh!

What you see here is what lozenges COULD be like - both a color, and a number, so that you can see the progression through our workflow more at a glance. Note that by using a unique identifier, such as a number, you also help make these ADA compliant. I highly recommend to Atlassian to either: a) re-add the ability to use custom links to our own custom icons for status, or b) create a system using your new lozenges that allows us to create nearly unlimited different "categories" of lozenge - that combine both a number and a color. (Actually, in my opinion you should do both. You shouldn't make everyone lock into your own thoughts about how to best show status. Implement good lozenges + allow users to use their own custom sets based on their own needs.) Thank you!

NOOOOOO! We just fixed this by creating our own custom icons for each status/workflow step (of which we have 15-16 steps) and now all we get is to choose from 3 colors?? Please, bring back our ability to use our own icons... BTW, we used color, plus a number for our icons. So we had 3-4 levels of green, 3-4 levels of yellow, 6-7 levels of red, and so on... simply having a choice between a few colors does not meet our needs.

Nick. I like the lozenges, but imagine if you had still used icons but only showed the icon instead of the status name. Multiple statuses often use the same icon, so you would never have known what the status of a subtask was. Using a color chip or icon alone is just not enough information in many cases.

I think the issue is not just that JIRA is replacing the issue icons with the issue lozenges; the bigger issue is that the "compact view" removes the name of the status entirely. I almost never looked at the issue status icons, so their replacement with something else is no real loss to me personally...but I used the actual status names an awful lot, and removing them (from, say, the subtask list) will decrease usability, seemingly without making any obvious gains in terms of the presentation or layout. Almost everyone has a 1200+ px wide screen these days, so it's not like horizontal real estate is in short supply.

In general, we believe lozenges provide greater visibility of the issue status than what the icons ever did. I appreciate all of your early feedback on the the 'chip' style. It's on my radar and I'm monitoring closely.

Regards,
Nick
JIRA Senior Product Manager

I just noticed at JRA-35317 that the status' category color is being used instead of the status name in the display of linked issues as well. So if I have two linked issues, one is Open and the other is Needs Review, then I can't tell that without hovering on each color chip. This will be hard to explain to customers.

I am glad to see that I am not the only person thinking "accessibility".

These v6.2 changes might look nice to some but represent a real step backwards for regulatory compliance. And compliance really does matter. Some organizations are not legally allowed to use software that fails compliance testing.

Bear in mind that some Atlassian customers might be using JIRA internally today and not really have a problem with accessibility compliance. But if they (say) would like to license JIRA Service Desk and alllow their external users to see JIRA then, suddenly, there could be problem where one did not exist previously. These external customers can be local government (or whatever) and have to follow different rules. So, Atlassian ends up losing sales. For what? Sexy lozenges?

I agree! I would also be surprised if this change did not also introduce another issue with ADA section 508 compliance regarding accessibility for the color blind (JRA-5574).

Priority raised to Major because there is no workaround to display the status names quickly in an issue with subtasks

For instance, which of the subtasks in this screenshot are Open and which are in some other status with the same Category and color?