rfleming@atlassian.com I agree with micah3. I went to fill out the survey and it is completely missing the point. There is nothing I can do with your survey that would give you any indication of what we actually want to do with the portal.

Too often, Atlassian use their own products in ways that the customers cannot do without extensive re-coding or extensions. If you want to make your customers happier, allow us to use your products the same way that you do!

Hey Rohan,

Thanks for the survey, but unfortunately the survey is too shortsighted. Based on that you would not satisfy our needs.

We want to be able to control the full experience. Similar to support.atlassian.com. The main landing page is a great example of this. With the ability to link into the JSD section and then within the JSD section then able to group different actual service desks.

In addition to this, I think that the ability to control the actual way that the JSD section is laid out is super important. heders, footers, side bars, select what jsds to show.

Hi all,

We are always looking for ways to improve the customer portal and have a few open questions around some of your branding/customisation requirements. We have created a quick survey to capture some of your feedback here: http://www.surveygizmo.com/s3/3335698/2017-Customer-Portal-Customisation

Thank you again for all your continuous feedback!

JIRA Service Desk team

Hello,

I created this plugin: https://marketplace.atlassian.com/plugins/com.prontop.service-desk-landingpage/server/overview

It may help you customize the Service Desk Landingpage/portalspage, such that you can add different information/html/macros, and even a categorized view of portals. Check it out

It may help on the problem you describe. I'm open to implement features you need, e.g. like i18n macro constants!

best regards from Pronto Plugins

Hi Relihan,
I'm fairly sure it's only against the TOS if you remove the attribution. There's no need to remove the attribution or links back to Atlassian. The solution/hack I've suggested is really just around more branding in the portal (colours, fonts etc.)
Happy to be corrected on the TOS point and I do agree it'd be much nicer to be able to simply include some custom CSS in the product, but since it's been closed off as Won't Fix I figured a workaround would have to do.

Nice work, however it would be ideal if we didn't have to hack things because unfortunately the method you proposed is against the terms of service. I got the following email from Atlassian:

White labeling of Atlassian products is not permitted as per our End User Agreement section 4.6:

4.6 Attribution. In any use of the Software, End User must include the following attribution to Atlassian on all user interfaces in the following format: "Powered by Atlassian", which must in every case include a hyperlink to http://www.atlassian.com, and which must be in the same format as delivered in the Software.

Here's a hacky workaround if it helps anyone.
http://www.glintech.com/blog/modifying-the-look-of-jira-service-desk-using-custom-css-nginx.html
You can inject custom css using nginx as a reverse proxy (and probably other reverse proxies).

I voted for the new one, however my original "feature" request MAR2015 comprised various things, incl. the request type icons etc.

nicely spotted guys bjorn2 & c.roser. You mentioned the removed portal logo icon option. Please vote for it here https://jira.atlassian.com/browse/JSD-1836

Shouldn't the resolution be "won't fix" instead of done? This hasn't been done right? Im confused.