After a bit of testing and searching, i got it working for JIRA Service Desk 3.2.

It seems that Service Desk 3.2 renders the portal different than 3.1 and didn't use the .soy file.

The portal seems be generated from customerportal.bundle.js which is in the jira-servicedesk-3.2.0-139 root folder.

To make the file a bit more readable i used: http://jsbeautifier.org

The line that needs to be changed is 16345:

Here is the complete customized line:

i += '<div class="cv-visible-portal">' + (u ? '<div class="cv-portal-item ' + (!u.logoUrl ? "cv-portal-no-logo" : "") + '"> <span class="cv-portal-round-logo aui-avatar aui-avatar-project aui-avatar-medium"> <span class="aui-avatar-inner"> <img src="' + soy.$$escapeHtml(u.logoUrl) + '" class="cv-portal-round-logo-img"/> </span> </span> <div class="cv-portal-info"><a class="js-portal cv-portal-item-link" data-id="' + soy.$$escapeHtml(u.id) + '" href="' + soy.$$escapeHtml(u.portalBaseUrl) + '"><span class="cv-portal-name cv-portal-link">' + soy.$$escapeHtml(u.name) + "</span></a>" + (u.description ? '<div class="cv-portal-desc">' + soy.$$filterNoAutoescape(u.description) + "</div>" : "") + "</div></div>" : "") + "</div>"

You will see that it uses the same tags as in the .soy file.

Regards,
Tim

Hello luca.sokoll,

i've added them. If you have tried it, i hope you have cleared your browser cache.
The added code is copied from the JIRA Service Desk 3.0 template files.

                            <span class="cv-portal-round-logo aui-avatar aui-avatar-project aui-avatar-medium">
                                <span class="aui-avatar-inner">
                                    <img src="{$portal.logoUrl}" class="cv-portal-round-logo-img"/>
                                </span>
                            </span>

Regards,
Tim

Tim - can you provide a screenshot(s) of this that shows it working for you? 

Currently i'm playing with Service Desk 3.1.

Step 1: Disable the Smart Portal and show the old design without logos but with description

https://jira.example.com/secure/admin/SiteDarkFeatures!default.jspa

# Add
sd.global.portal.rt.search.disabled

Source: JSD-3898

Step 2: Change .visiblePortals template in cv-visible-portals.soy

/**
* List of visible portals
* @param visiblePortals
*/
{template .visiblePortals}
<div class="cv-visible-portals">
    {if length($visiblePortals)}
        <div class="cv-visible-portals-list">
        {foreach $portalGroup in $visiblePortals}
            {foreach $portal in $portalGroup}
                <div class="cv-visible-portal">
                    {if $portal}
                        <div class="cv-portal-item {if not $portal.logoUrl}cv-portal-no-logo{/if}">

                        	<!-- Custom Code Start -->
                            <span class="cv-portal-round-logo aui-avatar aui-avatar-project aui-avatar-medium">
                                <span class="aui-avatar-inner">
                                    <img src="{$portal.logoUrl}" class="cv-portal-round-logo-img"/>
                                </span>
                            </span>
                            <!-- Custom Code End -->

                            <div class="cv-portal-info">
                                <a class="js-portal cv-portal-item-link" data-id="{$portal.id}" href="{$portal.portalBaseUrl}">
                                   <span class="cv-portal-name cv-portal-link">{$portal.name}</span>
                                </a>
                                {if $portal.description}
                                    <div class="cv-portal-desc">{$portal.description |noAutoescape}</div>
                                {/if}
                            </div>
                        </div>
                    {/if}
                </div>
            {/foreach}
        {/foreach}
        </div>
    {else}
    <p>{getText('sd.customerview.allportals.no.portals.message')}</p>
    {/if}
</div>
{/template}

What i not understand, that all old Service Desk design stuff is still in the code and available and Atlassian is ignoring that people dislike the very clean and simple design.

Don't forget to clear the browser cache.

Screenshot

 
Regards,
Tim

c.roser: Have you found a workaround?

Update: My suggestion works for 3.0.x

Regards,
Tim

Has anyone found a workaround to bring back the logos for JSD 3.1?

Please bring this back - we have 15 service desks and really need the logos - removing these sucks for enterprise

this sucks guys - sort it out!!!!

Tim's suggestion unfortunately will not work for Jira SD 3.x.
I'm currently testing my workaround for V 3.19 and will post it here if it is successful.

I just want to reiterate what others have said about this. Having the logos really helps our users to navigate more easily. Please bring them back.
Attached is what ours looked like before the upgrade.

Hi @shamid, @jrahmadiputra, @jaguilar,

even though I appreciate all innovations Atlassian brings into their products (e.g. smart graph), the recent change in the Help Center and customer portal was one of the worst decisions!

After introducing the super-intuitive customer portal with icons and multiple service desks in the Help Center in JSD 2.x we made the decision to use JSD in the production and convinced our customers for it. Our Help Center currently also represents a catalogue of services provided to our customers.

I am very disappointed with the Help Center and customer portal in JSD 3.x. We actually can't update to JSD 3.x if the Help center now dynamically displays only the selected Request types based on their usage. The new Help center would be extremely confusing for our customers. Many of them who finally got familiar with the customer portal expect to find the things in the same places as previous time.

Please, get inspired by the Confluence developers - when they introduced the new dashboard, there was still an option 'Give me the old dashboard' left and provide feedback.

I like to ask you to add the option to switch to the previous Help Center and customer portal as soon as possible (JSD-3527).

Thank you.

The new help centre is problematic. It was much better when it showed the search bar and each portal with a nice logo in a grid, like my screen shot.

Now, it shows most recent request types used, which we have no control over. Meaning people just come straight to the portals page and choose 'general issue' without searching or bothering to do anything else, meaning all the other request types don't even get seen.

shamid@atlassian.com Do you have a timescale for when the new Help Center will be released for Server? We're ramping up towards the launch of Service Desk internally so if this is going to be "soon", it would merit us holding off but if it is going to be several months still ...

Thanks.

Hi shamid@atlassian.com,

I believe the ongoing work on "smart search/suggestion-oriented experience" is excellent, is in the right direction (wish we had it sooner on server as well) . Searching request types was one of the features requested strongly by earlier adopters of the JSD. However I don't see the reason to scrap the option to have the full list of service desk (with icons), after all not every organization has a very large number of service desks to become a problem.

Cheers,
AP

Dang it, I always post things while logged into the wrong account. The above comment was mine.

"Thanks for the update, whilst I can see where you're coming from - you can see from my screen shots that we clearly did utilise this feature correctly and with a great benefit to us. Therefore I think you should make it an optional feature which is, by default, switched off. I think totally removing it is unnecessary."

Thanks for the update, whilst I can see where you're coming from - you can see from my screen shots that we clearly did utilise this feature correctly and with a great benefit to us. Therefore I think you should make it an optional feature which is, by default, switched off. I think totally removing it is unnecessary.

Hi guys,

We understand that this is a loss in functionality for some of you and we appreciate the screenshots you have submitted to illustrate the problem.

The goal of the Help Center is to help take end users to the right spot.

As jhuynh mentioned earlier, we found that many admins did not set meaningful icons or even bother to change the default descriptions. This meant that the Help Center experience was a sea of meaningless "Welcome! You can raise a ___ request from the options provided" for many end users.

We have since changed the Help Center design to have a smart search/suggestion-oriented experience: https://confluence.atlassian.com/display/SERVICEDESKCLOUD/Using+the+help+center (available on Cloud now, and in an upcoming release for Server).

The new browse experience surfaces popular service desks and recent request types. We have found that this produces a much better Help Center experience than a list of service desks, especially as the number of service desks grows. That said, there is still the possibility to browse all service desks - and in this case it does make sense to add back icons and descriptions - so we will leave this suggestion open. We will post any further updates on this issue.

Thanks again for your feedback!

-Shihab

Voted, unbelievable that Atlassian is removing functionality...

We are preparing to launch our Service Desk next week, and we are so very disappointed (after our upgrade to SD version 3 this weekend) to find that we no longer have the icons on the main customer portal page. Not a single member of our team is pleased with this change. We agree with the comments above, that having no icons on that page makes the portal look unfinished. Everyone who helped make the decision to move to JIRA Service Desk (away from our current platform) was very happy that it had the option of these icons (before v3).

Before our upgrade to v3, we completed a round of SUS testing on the Service Desk portal, and everyone was really happy and positive about the icons on the front page. We achieved an incredibly high SUS score of 89, and it was higher because of those icons. It was actually called out in the test results.

We are extremely disappointed that we will now have to launch without the icons that we went to all the trouble to have created, specifically for this purpose. Downgrading isn't an option for us, because we need the search functionality that will soon be released with v3.1.

Why wasn't this implemented in version 3?! This simply needed reverting back to how it was before. Please provide an update as to when this will be put back.

Hi all.
I also voted for this issue.
We have 33 portals and it's hard an not comfortable to navigate between them without logos.

Yeah, this is surprising to see it is intentional, thought it was a bug of configuration issue on our end that the help portal would be so bare and unfriendly. It looks unfinished now.

I just can't believe that you guys removed this feature in the first place...
You said most of your customers don't use project logos but how about those who actually use it.

Very dispappointing.

#BringOurLogosBack

Voted and watched - thanks @Aggelos

Agree 100% with luca.sokoll. What was the rationale for removing it in the first place?

Just spotted that the option is included in a new issue JSD-2170 Help Center - Body Customization|

2) display/hide individual project logo

So please everyone vote for it!

Can you please bring this option back? Our Service Desk Portals page looks bland and boring now.

Original -
Current -

We have a lot of Portals and it would make it easier for our customers to choose the right one. Furthermore it increases the value of the portal. Without the images it looks a bit monotonous.

I need this feature restored also.

Having custom logo for each portal allowed the user to quickly navigate to each service desk a provided much more professional look to the entire portal. i understand the reasons you mentioned for logo removal, however those could be solved by (for example) allowing the logo to be optional - not removing existing functionality the SD customers already expect and are used to completely.

Hello Joseph,
the cases you describe might be valid. However: The choice to allow a custom portal logo or NOT is not a big thing and will avoid those cases you described. It was implemented already before. Let the customer choose if a custom project logo should be a applied or not.
If you configure a service desk properly and know what you are doing you will not end up with uploading "flower images"
Please reinstate this option again.

Hi Guys, thank you for your feedback. We agree with you that having a visual queue to separate out projects is important.
Prior to 2.4 release we have noticed several patterns:
1) that majority of our customers do not have individual project logos - end up uploading random photos like flowers and soccer balls.
2) customers didnt upload any project logos at all.
3) duplicate logos for projects

In all of the mentioned cases made their help center appears broken.

Also request that the logos are also clickable links to the service desk.

I agree, it was good to have the logos as visual cues for each service desk.

Hello to all, why this has been removed?
From what I can see: the css class for the logo is still there and it was good to have the logos there as they quickly guided Portal users to the appropriate portal rather than having to read the text. Could you please reconsider to re-integrate the logos?

Hi jrahmadiputra,

This is a recent redesign on the main portal. I think we forgot to provide public documentation notes for this change.

cc lpham, skarp

Wrong Screenshot name as it is supposed to be JSD241.PNG