features activation after Upgrade

[mariemq]

I'm looking for some clarification on the upgrade processes and release strategies for Jira Cloud:

1. Feature Activation: How does the activation process work for new features? Are there specific circumstances that dictate whether features are automatically activated or require admin intervention?

[Dr Atul G- LNG]

Hi @mariemq 

Hi @mariemq 

There are few features which get added after upgrade and few need to enable. Like Next experience, in earlier release it was not default but now from Vancouver onwards it is default with upgrades. So you need to see what new features are coming and are they independent or need to enable manually.

To do this, upgrade Dev first and verify the stuff.

[Rakesh18081]

HI @mariemq 

n Jira Cloud, the activation process for new features depends on the type of feature and Atlassian’s rollout strategy. Here’s how it generally works:
- Automatic Activation: Some features are enabled by default when Atlassian releases them. These typically include UI enhancements, security updates, and backend improvements that don’t require user intervention.
- Admin-Controlled Activation: Certain features require manual activation by a Jira administrator. These are usually advanced functionalities like parallel sprints, roadmap views, and backlog management, which can be toggled on or off in Project Settings > Features.
- Gradual Rollouts: Atlassian often releases features in phases, meaning some users might get access earlier than others. This is done to monitor adoption and address any issues before a full rollout.
- Beta & Early Access Programs: Some features are available through Atlassian’s beta programs, where admins can opt in to test new capabilities before they are widely released.

Regards

Rakesh Agarwal