For most teams, native JSM portal customization on Cloud is solid enough now that you don't need a third-party frontend like Refined unless you have a specific need for a fully branded, marketing-site-like experience. Adding well designed icons for requests types and a banner would add so much to the look natively.
A quick way to decide:
- Go native if you mainly need a clean, functional self-service portal: Cloud's built-in branding, custom layouts, and forms cover most of what teams actually ask for, and you avoid adding another system to maintain and keep in sync with Jira permissions/updates.
- Consider Refined if you need heavy visual/brand control across multiple portals unified under one experience, or navigation that behaves more like a marketing website than a support portal. Worth knowing going in: Refined Cloud is a parallel site builder, not an overlay like the old Server/DC version, so it's more setup and ongoing maintenance than people expect coming from Server.
- Either way, budget time for keeping the frontend in sync with JSM changes: that's the maintenance cost that surprises people most, regardless of which option they pick.
What's actually driving the need for a different frontend in your case? Is it branding/visual control, unifying multiple products under one portal, or something else? That would point pretty clearly to one option or the other.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.