Who made the bad decision to de-emphasis the Jira numbers on the Backlog and Sprint boards?

[Edie Hovermale]

I need the Jira NUMBER to be more visible in the Jira cards on the Agile boards and specifically on the Backlog board. You changed the design and I can barely see the numbers. Worse yet in the Backlog board I now am forced to scan my eyes back and forth to connect the JIRA number with the summary. Please move the numbers back to the front and make them more visible or better yet make it configurable so I can do it. I am very frustrated that you push changes like this instead of giving me the option. This change is a very big deal to me and my team. Why would I want to have to read through the entire summary? Engineers use numbers to make it faster and easier when referring to stories and bugs. Now the numbers are barely visible and located where I am forced to scan. Can you do other things with all of your engineering time like fix bugs instead of mess with the UI. I am so very frustrated with the Atlassian JIRA. Urgh!!!!!

[Sed · Accepted solution]

+1 - This is now impacting our team as well. 

[Nic Brough -Adaptavist-]

Answers is not used as a source for requests or given any weighting when Atlassian do their planning.  If they happen to find a thread useful, then it gets raised in JIRA.  +1 and shouting here is not relevant, find the right JIRA issues and vote there

[Matthew Schultz]

+1

[Sam Hall]

For anyone who hasn't seen, there's now a blog post from Atlassian about this, which includes references to the suggestions/improvement/bug issues they are working on as a result of feedback: https://confluence.atlassian.com/jirasoftwarecloud/blog/2016/12/new-design-of-jira-software-issue-cards

They are also updating the following issue with information about updates made:

https://jira.atlassian.com/browse/JSW-15331 

There is also this suggestion, which is covers moving the issue key to the left:

https://jira.atlassian.com/browse/JSW-15521

These are best things to comment & vote on, rather than this question/answer thread..

As @Nic Brough [Adaptavist] mentioned +1's and comments on this question/answer don't make much difference. It's the 'Bug' and 'Suggestion' issues in the JSW project that matter more : https://jira.atlassian.com/projects/JSW 

The Atlassian blog post also says "If you have any feedback or suggestions, let us know by clicking on the Feedback icon on the header." - I think that means the bullhorn / megaphone icon that appears at the top bar in JIRA, next to the search box (for example see: https://jira.atlassian.com).

[Adrienne Meisels]

Not only do I want to be able to put the JIRA number back at the beginning of the line, but also it is now almost impossible to see which tickets are closed as only the JIRA number, not the whole line, is stricken through. Either revert back to a complete strikethrough or shade the closed tickets in a different color so it's easy to discern which ones are closed and which ones are opened when scanning the sprint.

[Edie Hovermale]

Yes, it is now harder than ever to see what is going on in a project. I have had to create a lot of quick filters but that limits seeing everything as a whole.

[Nic Brough -Adaptavist-]

I'd raise this as a suggestion (or, frankly, given that it's broken the way a lot of us work, a bug), on jira.atlassian.com and see what Atlassian have to say about it directly.

If you do that, let us know so we can all vote on it!

[Edie Hovermale]

Hey Nic,

I was thinking the same thing. I contacted the customer support rep at Atlassian a couple of hours ago and asked him to make it a bug. I have not heard back yet. 

[Adrienne Meisels]

I filed it as a bug and they told me that I had to post it on the suggestion page.

[Edie Hovermale]

There's a suggestion board? Adrienne, did you get a chance to post it?

[Adrienne Meisels]

mmm ... maybe it's not a suggestion board ... there's a lot of discussion here (a lot of discussion by everyone OTHER than Atlassian ... would be nice if one of their reps would have piped up by now to let us know we're being heard): https://jira.atlassian.com/browse/JSW-15331

[Nic Brough -Adaptavist-]

They do pick stuff up here, but that doesn't mean you'll get a response or any action.  It's the JSW issues that matter - +1's and extra "I want" on Answers don't make any difference.

[Edie Hovermale]

I have a call set up for tomorrow with a customer support rep. I will give him all the information from all comments on this and from the JSW. I will also point him to this discussion. I am not optimistic that anything will get done though. Atlassian support is a black hole.

[Edie Hovermale]

I live in SF and may just walk over to their offices and see if they will let me talk with someone. I did that once before.

[Jason Krause]

Agree. Changing the Backlog Board for no reason and no apparent benefit was a horrible decision. You did not make it better you made it worse. If you are going to do a change like this give your users the ability to revert back or customize it themselves. 

For the record this has nothing to do with the cards redesign before you ask as that is all your support team seams to be able to talk about.

[Edie Hovermale]

Hey all,

I just got this from Greg Keefer of Customer Support:

"I did speak with a developer and the impression I got was that this change was not something that was going to rolled back."

Not sure how we can get any help from Atlassian. I don't know why they would not fix an issue that so many teams are having with an "Enhancement" they made to make our lives better.

[Edie Hovermale]

Please go to:

https://jira.atlassian.com/browse/JSW-15521

And vote for this and comment. This is the only way to get any attention on an issue.

Thanks

[Edie Hovermale]

Paulo (the Atlassian Customer Support Rep) sent a follow up today. Here it is:

---

Hi, Edie.

Thanks for your updates and for your time on the call yesterday!

I have talked to my leader in order to understand what could be done regarding your feedbacks and indeed we agree that are some points where we can enhance our application, we'll need some time to see the best alternatives in this way.

Indeed while we work with our team on that I should post you some workarounds that will help you to manage your tickets on the backlog and on the sprint.

I believe we should have an update on the next business day, and again, sorry for the inconvenience.

Best,
Paulo

---

[Edie Hovermale]

Just a quick update. I had a very nice conversation with a customer support representative today, Paulo Miguel. He was very attentive and understanding. He heard our concerns. I also sent him info including a link to this thread and to JSW-15331 and JSW-15336. Paulo will take our concerns to the next level for discussion. He said he will get back to me tomorrow with an update.  

[Randy]

This was logged as a bug and i'm pretty sure Atlassian is working on a way to address the missing issue numbers.

https://jira.atlassian.com/browse/JSW-15336

[Nic Brough -Adaptavist-]

As I said, Answers is not used as a source for requests or given any weighting when Atlassian do their planning.  If they happen to find a thread useful, then it gets raised in JIRA.  +1 and shouting here is not relevant, find the right JIRA issues and vote there (don't bother ranting, that's ignored, make a case.  I've voted, but not commented because other people have said it better)

Whomever told someone to come here to request a fix for this was, I'm afraid, misleading.

[Jason Krause]

So has anyone actually got someone to admit this a problem and not a feature up and state that they will address it?

I feel like we are all getting run around in circles! Make a bug ticket, oh wait no don't do that post a question and let it get voted on. Oh wait sorry you need to do a support ticket. Around and round we all go. 

[Team Web CMS Services]

To really answer the question  - it was Jim - it always is - and I agree totatlly.

[Adam Brundrett]

+1.  The new backlog view is revolting and seems designed to make our lives harder.

[Edie Hovermale]

I agree, I am also not bothered about getting the old card back. The customer support rep entered the issue and didn't capture it correctly. I do however want the Issue # to be prominent (not gray) and close in proximity to the summary.

[Nic Brough -Adaptavist-]

I'm not sure I'm bothered about "getting the old card layout back", but I do want the issue key to be shown in full and all the time.

[Seth W Rosenfeld]

This Question was entered as a result of discussion on https://jira.atlassian.com/browse/JSW-15331, in case anyone who is new to the discussion wants to loop back and vote for the issue.

[Jennifer Marlett]

+1

[JP Foerster]

+1. //jp

[Seth W Rosenfeld]

+1 - why make a change like this without allowing user configuration to manage the view directly?  Very frustrating.  This type of thing drives me to consider more specialized workflow option for our products (games). 

[Sarah Shepard]

Ditto!