You might find a recent article posted via LinkedIn useful - it outlines the "Best Apps for Jira Service Management in 2026" across the various key features in JSM: - Service Request Management - Knowledge Management - Incident Management - Problem Management - Change Management - IT Asset Management External link: https://www.linkedin.com/pulse/best-apps-jira-service-management-2026-ultimate-guide-kate-pawlak-k3kdf/ The article is by a Marketplace partner, so there's an element of upsell in it, however the author is Kate Pawlak who I regard as a headline act in the Atlassian world.

I try to use common, shared workflows whenever possible to promote consistency across teams and reduce our maintenance overheads. On occasions where I need the workflow to behave differently for different teams but still within the SAME workflow, I create a “branch” in the workflow and apply conditions on each branch so that the transition to that branch is only available to a particular team. Then I can use other properties (eg. transition screen, validators) on the relevant branch to add the required behaviour. For the “branching”, use a Value Field condition and add the branch criteria on the options screen - eg. Field to compare against such as a team identifier, value, comparison type. It’s a bit messy to do, but it does work! However you’ll need to consider the pros & cons of creating a separate workflow for ease or applying this kind of technique so that you can keep everything in the same workflow.

Hi - yes, you can use this technique to restrict certain transitions to a designated team, and wrap the extra validation needed for that team into the transition (eg. transition screen and validators for mandatory or updated fields). So depending on the team /field setting in the work item then the transition may or may not be shown as being available in the workflow status menu of the work item. Be aware that if your users use the view workflow function in the workflow status menu then it will show them all the “branches” - so that may confuse them, so you’ll need some user comms around this, or disable the view workflow privilege via the permission scheme. I’d also recommend having this config documented somewhere for your Jira Admin colleagues as it’s the kind of thing that’s not immediately obvious until you look closely under the covers!

Hi @Corey Glaude - when you add the Goals field to your Jira work item screens, then it allows the work item to be linked to more than 1 goal (ie. it's a multi-select field). The official Atlassian documentation for Goals isn't too bad - have you seen these? I think Atlassian are due to release a feature that allows you to configure Goals based on whatever framework your company uses rather than having to apply a few workarounds as at present. Also, there's a free Atlassian webinar on 18 & 19 November which you might find useful: [Webinar] Drive goal-aligned work with Goals & Projects Join us for our upcoming webinar where we’ll cover proven goal-setting practices, show how platform apps like Goals and Projects keep teams aligned and accountable, and share practical tips for tracking progress toward what matters most. Register now

Hi @Corey Glaude - the upcoming changes to allow Goals to be configured based on your organization’s preferred framework and terminology (eg. OKRs) has been announced and is due to start rollout on 1st December 2025. See post in Atlassian Community: https://community.atlassian.com/forums/Atlas-Group-articles/Goal-Types-and-better-support-for-OKRs-are-coming-soon/ba-p/3151925

Hi @Oresta Tymchyshyn, Few additional comments to expand on what has been added already... 1) You can subscribe to the official Atlassian Cloud Roadmap that was mentioned above and get a weekly email digest of changes. 2) I find the Cloud Changelog also referenced above very useful - it pulls in all the basic info from the official Atlassian Cloud Roadmap but presents it in more user friendly way, and with the ability to download the info and search previous entries. Also, If you are on a continuous release track (ie. "changes are added as soon as they're available"), then even though a new feature has been released then it does not mean it has actually been deployed to your site(s) as Atlassian deploy changes on a rolling basis, region by region - and so a change take days, weeks or even months to be deployed to your site! If have Org Admin privileges, then under Apps > Platform Experiences > Release Management > App Updates you will get a list all the changes, but you can then drill down into each change and access a Rollout Schedule screen to see if/when it was actually been deployed to your site(s).

Hi @Rachel Park Brayboy - Confluence Cloud has a feature called "Company Hub" which you might find useful as a landing page to provide users with key information and signposting to other Confluence spaces. I've attached a couple of examples. This feature is only available in Confluence Premium & Enterprise subscription plans, but if you don't have that then I believe some of the underlying macros it uses are also available as standalone macros in Confluence Standard. It also works with the third-party apps like Mantra and Karma that were mentioned in other replies here. You can see examples of Company Hubs that Atlassian published from a competition they held last year. Atlassian have also published 5 Tips for Creating a Dynamic Intranet for Your Org which may give you some ideas.