confluence.atlassian.com
Open in
urlscan Pro
108.138.36.78
Public Scan
URL:
https://confluence.atlassian.com/cloud/blog/2024/11/atlassian-cloud-changes-nov-18-to-nov-25-2024
Submission: On November 26 via api from US — Scanned from DE
Submission: On November 26 via api from US — Scanned from DE
Form analysis 0 forms found in the DOM
Text Content
Products
ATLASSIAN CLOUD SUPPORT
* Documentation
* Resources
* Search
* Log in
* * View account
* View requests
* Log out
* ...
PRODUCTS
* JIRA SOFTWARE
Project and issue tracking
* JIRA SERVICE MANAGEMENT
Service management and customer support
* JIRA WORK MANAGEMENT
Manage any business project
* CONFLUENCE
Document collaboration
* BITBUCKET
Git code management
See all
RESOURCES
* DOCUMENTATION
Usage and admin help
* COMMUNITY
Answers, support, and inspiration
* SUGGESTIONS AND BUGS
Feature suggestions and bug reports
* MARKETPLACE
Product apps
* BILLING AND LICENSING
Frequently asked questions
* Log out
* Log in to account
* Contact support
* Training & Certification
* Cloud Migration Center
* GDPR guides
* Enterprise services
* Atlassian partners
* Developers
* User groups
* Automation for Jira
* Atlassian.com
To get a weekly digest of these Cloud Release Notes, visit the
Email and Privacy Preferences page and check the box for Cloud Release Notes.
* PAGE
* Edit Blog
* VIEWPORT
* Manage Viewport
* CONFLUENCE
* Dashboard
* Space Directory
* People Directory
* Atlassian Support
* Atlassian Cloud
* Documentation
* Blog
* Blog Posts in 2024
* Blog Posts in Nov 2024
* Atlassian Cloud changes Nov 18 to Nov 25, 2024
ATLASSIAN CLOUD CHANGES NOV 18 TO NOV 25, 2024
These changes have recently been rolled out to Atlassian Cloud sites.
Changes labeled ROLLING OUT are being gradually rolled out and may not be on
your site just yet.
JUMP TO...
* Atlassian Administration
* Jira platform
* Jira
* Jira Service Management
* Jira Product Discovery
* Confluence
* Bitbucket
* Compass
* Atlassian Analytics
ATLASSIAN ADMINISTRATION
Atlassian Administration is where you manage your Atlassian organization,
including user access to products, security settings, and billing preferences.
GET SECURITY ALERTS IN YOUR LANGUAGE
ROLLING OUT NEW THIS WEEK
Guard Detect generates alerts when suspicious user user activity or sensitive
data is detected.
You can now use Guard Detect in more than 20 languages. Like Atlassian
Administration, it uses the language preference set in your Atlassian account
profile.
Guard Detect requires Atlassian Guard Premium.
DELETING EXTRA MOBILE APP POLICIES THAT WE DON’T ENFORCE
COMING SOON
We currently allow you to create one mobile app policy per organization.
Some of you may have created multiple mobile app policies with the Admin REST
API. Even if you created more than one, we only enforce the most recent policy.
Effective 04 December 2024, we will delete any extra mobile app policies that we
don’t enforce. You will see the policy we deleted in audit logs.
You can use the Admin REST API to view deleted policies for up to 30 days.
We are making this change in order to enable the introduction of a new update:
you will soon be able to create one mobile app policy per app.
Understand mobile app policies
TRACK ROVO USAGE WITH NEW INSIGHTS ON AGENT INTERACTIONS
COMING SOON
You can now view the number of requests users have sent to Rovo Chat or Agents.
Usage metrics also include the percentage of unused quota left for the month.
For a limited time, usage beyond quotas will not incur additional charges.
How Rovo usage quota works
To view quota usage for Rovo requests:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Security then Insights.
3. Navigate to the chart named Requests sent to Rovo.
PREVENT PEOPLE WHO ARE NOT LOGGED IN FROM VIEWING CONFLUENCE PAGES
ROLLING OUT NEW THIS WEEK
Data security policies allow you to control how users, apps, and people outside
the organization interact with content, such as Confluence pages and Jira
issues.
You can now use the anonymous access rule to prevent people who aren’t logged in
from viewing Confluence pages.
Previously, the rule blocked anonymous access to Jira issues and in policies
that cover Products in Confluence. Now, it will also block access to Confluence
pages within policies that cover spaces and projects.
The anonymous access rule requires Atlassian Guard Standard.
To create a new data security policy or view existing policies:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Security > Data security policies.
APPLY SECURITY SETTINGS TO DIFFERENT MOBILE APPS
COMING SOON
You now have the flexibility to set up different security policies to meet the
security needs of specific Atlassian mobile apps. A mobile app policy allows you
to apply security settings to all or one mobile app at a time.
Your default mobile policy applies security settings to Confluence, Jira and
Opsgenie. To apply different levels of security to one of these mobile apps, you
can create a mobile app policy or edit your default mobile app policy.
To create a mobile app policy:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Security > Mobile app policies.
3. Select Create mobile app policy or Add mobile app policy and follow the
prompts*.*
To edit a mobile app policy:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Security > Mobile app policies.
3. To edit a mobile app policy, select Actions (…) and follow the prompts*.*
APPLY A DEFAULT CLASSIFICATION LEVEL FOR ALL CONFLUENCE PRODUCTS IN YOUR
ORGANIZATION
COMING SOON
Data classification is the process of categorizing the sensitivity of
information.
Apply a default classification level that can be enforced across all your
Confluence products in your organization. This classification level will be
applied to all unclassified content within Confluence.
This process requires Atlassian Guard Premium.
To apply a default classification level for all Confluence products in your
organization:
* Go to admin.atlassian.com. Select your organization if you have more than
one.
* Select Security > Data classification
* Select More actions (•••) > Manage settings
* Choose the classification level
* Select Update
BRAND YOUR JIRA PRODUCTS WITH A CUSTOM DOMAIN
ROLLING OUT
You can now use custom domains to brand your Jira products. Custom domains
provide easy-to-remember URLs for your users to access your products.
You can create a custom domain if you have a Jira Premium or Jira Service
Management Standard plan.
Previously, this feature was only available for Jira Service Management help
center. Tell me more about custom domains
To create a custom domain:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Products > Product URLs.
3. Select Add custom domain. This is only visible if you have an eligible
product.
4. Review the Before you add a custom domain page, and select Next.
5. Select which product you want to access from your custom domain.
6. Follow the prompts to specify your domain. You’ll need to enter two
subdomains and a domain.
7. Enter a Redirect URL. This is optional.
8. Review changes and select Create domain.
CREATE CUSTOM DOMAINS FOR YOUR JIRA PRODUCTS
ROLLING OUT
We removed keyword restrictions when you create custom domains. You will no
longer have a fixed list to select keywords for subdomains. Instead, you have
the ability to manually enter your own subdomains.
Jira family products have also been given added support. You can now select Jira
products from the dropdown menu when you create a custom domain.
To create a custom domain:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Products > Product URLs.
3. Select Add custom domain. This is only visible if you have an eligible
product.
4. Review the Before you add a custom domain page, and select Next.
5. Select which product you want to access from your custom domain.
6. Follow the prompts to specify your domain. You’ll need to enter two
subdomains and a domain.
7. Enter a Redirect URL. This is optional.
8. Review changes and select Create domain.
DATA RESIDENCY FOR MARKETPLACE APPS
ROLLING OUT
When evaluating data residency for your apps, you might see some apps listed as
"No action available."
This means that some app partners declare that their apps don't need to be
pinned or migrated because their apps exclusively store data within the
Atlassian product. Another reason is that the apps may not store any data in the
scope of the Marketplace partner's data residency policies.
To request a data residency move for your apps, you will have first to move your
product. Learn more about how to move your product from one location to another
Once your product has been pinned to your selected location, you can move your
eligible apps to the same location. Learn more about data residency for
Marketplace apps
WE’RE REPLACING JIRA SOFTWARE WITH JIRA IN CSV EXPORTS
ROLLING OUT
We’re bringing together Jira Work Management and Jira Software to make Jira your
one tool to plan and track work.
As a part of this, we’re replacing the "Jira Software" header with "Jira" in the
CSV files you export.
We recommend checking and updating any scripts that may be affected by this
change.
COPY SPECIFIC JIRA SERVICE MANAGEMENT AND JIRA WORK MANAGEMENT PROJECTS TO YOUR
SANDBOX
ROLLING OUT
Copy only the projects you need to save time setting up your Jira Service
Management and Jira Work Management sandbox. Understand how to select data to
copy
To copy specific Jira Service Management and Jira Work Management projects from
your production to its sandbox:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Products > Sandbox.
3. Select Copy production data for the Jira Service Management or Jira Work
Management product.
4. Select Specific projects.
5. Select the service or work management projects you need.
6. Follow the prompts to copy data to your sandbox.
More about what we copy to sandboxes
WE’RE REPLACING BEACON WITH GUARD DETECT
ROLLING OUT
This update only applies to organizations that participated in the Beacon or
Atlassian Information Security beta.
Beacon (beta) will soon be part of Atlassian Guard Premium. Read the blog
We’re replacing ‘Beacon’ with ‘Guard Detect’ in the CSV files you export. The
name of your groups (such as beacon-admins) will not change.
In Atlassian Administration, you’re able to export CSV files for:
1. Managed accounts
2. Audit logs
3. External users
4. User API tokens
5. Authentication policies
We recommend checking and updating any scripts that may be impacted by the
change.
ACCESSIBILITY AND STYLE IMPROVEMENTS TO TABLES AND PAGE LAYOUTS
ROLLING OUT
We restyled tables and updated the layout of pages. This improves accessibility
and readability in Atlassian Administration.
You can see the changes on most pages in admin.atlassian.com.
GET THE PRODUCTS YOUR TEAM HAS REQUESTED, FASTER
ROLLING OUT
You can now review and approve new product requests from your users and add them
to your organization, all from one place in admin.atlassian.com.
This is available for Confluence, Jira, Jira Service Management. Coming soon to
Bitbucket.
You’ll still have the option to deny product requests or mark them as under
review.
How to review product requests
To approve product requests:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Security then Product requests.
3. Find the product request, and select Review request.
4. From the product request, select Approve.
5. Read the information and select Next to continue.
6. Choose a name for the new site.
7. Select Accept and add product to finish. We’ll email the requestor to let
them know you approved their request.
It can take a few minutes to create your new site and product. If you don’t see
the new product immediately, check Products after a few minutes.
Once you can see the new site and product, invite the requestor and any other
team members that need access.
MANAGE LOOM IN ATLASSIAN ADMINISTRATION
Loom administration is now part of Atlassian Administration for existing
Atlassian customers and new Loom customers. You can sign up for a Loom
workspace, grant product access to Loom, and update user access settings for
Loom from Atlassian Administration. You can also change your plan and billing
details for Loom in Atlassian Administration.
Loom admins can continue to manage security settings for their workspace in Loom
via Settings > Workspace > Security.
To add a new Loom workspace to your organization or view your existing
workspaces created through Atlassian:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Products. You’ll find existing Loom workspaces you created through
Atlassian and any other Atlassian products in your organization here.
3. Select Add product and follow the prompts to add a new Loom workspace.
SEE WHAT’S HAPPENING ACROSS YOUR ORGANIZATION WITH YOUR NEW OVERVIEW
ROLLING OUT
Get an enhanced idea of what’s going on across your organization with our new
overview page at admin.atlassian.com. Quickly find your most important tasks,
monitor what’s happening with insights, and explore new features.
AUTOMATE YOUR RESPONSE WHEN SENSITIVE DATA IS DETECTED
ROLLING OUT
Guard Detect sends an alert when someone updates a Confluence page containing
certain types of sensitive data, such as credentials, financial, or identity
data.
You can now harness the power of Confluence automations to streamline your
workflow when sensitive data is detected. Build your own rule using the new
content scanning alert trigger, or try one of the templates to get you started.
Not sure how automations would help your workflow? Here’s some ideas:
* Classify the page that contains sensitive data.
* Restrict the page and add a comment or send an email to the actor to explain
your company's policy on sensitive data.
* Create a Jira ticket to track the next steps for cleaning up the data.
You can configure the trigger to perform an action when any content scanning
alert is generated, or just for specific alerts, such as API keys or credit card
numbers. Thanks to the huge number of actions and conditions available in
Confluence automation, the possibilities are endless.
How does automation work with Guard Detect?
The fastest way to get started is to use a template:
1. In Confluence, go to Automations.
2. Select the Templates tab.
3. Select the Respond to security alerts category
4. Select a template and follow the prompts to configure it.
You’ll also see an option to add an automation rule in your next content
scanning alert.
We suggest you create a rule in a test space first. Once you’re happy with the
rule, you can create a global rule. If you have multiple Confluence instances,
you’ll need to configure the rule in each instance.
Content scanning alerts are available with Atlassian Guard Premium. Automation
is available with a Confluence Premium or Enterprise plan.
PREVENT YOUR TEAM FROM USING NEW BITBUCKET WORKSPACES WITHOUT YOUR APPROVAL
COMING SOON
You can now proactively manage product requests for Bitbucket from
admin.atlassian.com. This feature provides you with more oversight to control
Shadow IT and billing.
After you select admin review required, you can approve or deny new Bitbucket
requests from your managed accounts. This gives you greater control over where
your team does their work.
This is available for Bitbucket as part of a beta program. It’s also available
for Jira, Jira Service Management, Confluence, and Trello with an Enterprise
subscription.
More about product requests
To manage product requests for Bitbucket:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Security > Product requests.
3. Select Request settings. If this is your first time updating these settings,
you may need to select Update request settings.
4. Next to Bitbucket, select Require admin review under the Request setting
dropdown.
The next time one of your managed accounts tries to sign up for a product,
they’ll receive a prompt to enter a reason for their request. After they create
the request, all organization admins receive an email, letting them know someone
created a request.
ROVO CUSTOMER ADMINS CAN NOW ADD BOOKMARKS
ROLLING OUT
Admins (organization, site or product) on sites with Rovo can now add bookmarks
to highlight particular URLs in Rovo Search, based on specific search terms. You
can bookmark any URL - it doesn’t need to be in your Atlassian products or
previously found in search.
There are two different methods to add bookmarks depending on whether you are a
organization admin, or a site/product admin.
How to add or edit Rovo Search bookmarks
PREVENT PEOPLE WHO ARE NOT LOGGED IN FROM VIEWING CONFLUENCE PAGES
ROLLING OUT
Data security policies allow you to control how users, apps, and people outside
the organization interact with content, such as Confluence pages and Jira
issues.
You can now use the anonymous access rule to prevent people who aren’t logged in
from viewing Confluence pages.
Previously, the rule only blocked anonymous access to Jira issues. Now, in
policies that cover Products, it will block Confluence pages as well.
The anonymous access rule requires Atlassian Guard Standard.
To create a new data security policy or view existing policies:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Security > Data security policies.
JIRA PLATFORM
Changes in this section usually apply to all Jira products. We'll tell you in
the change description if something is only for a specific Jira product.
UPDATES TO FILTER NAME SEARCHES
COMING SOON
We’re updating the filter name searches in dashboards and the filters page to
provide consistent and predictable results.
Previously, filter name searches used the JQL text search syntax, which produced
inconsistent results when the search term contained certain special characters.
Now, search results will display all filters that contain the search term.
SIGNING UP FOR CONFLUENCE FROM JIRA JUST GOT EASIER
ROLLING OUT NEW THIS WEEK
If you’re using Jira and don’t have Confluence you might see a prompt to try it
out. If you select this prompt you will go through a signup flow. Previously,
this flow was full-screen and used an older style of Atlassian branding.
The flow has been updated with new branding. It also opens on a smaller popup
screen that overlays your Jira screen.
The popup will vary depending on which Confluence plan you’re signing up for.
DEPRECATION OF JQL SEARCH AND EVALUATE EXPRESSION ENDPOINTS
NEW THIS WEEK
Over the years, Jira has grown, and teams are using the tool on a larger scale
and in more complex ways. JQL is one of the core capabilities of Jira, however,
our JQL APIs are being challenged by the scale and complexity of how they're
being used. JQL needs to evolve to remain reliable, performant, and scalable to
serve bigger, more complex use cases.
The mentioned endpoints expose parameters that aren't compatible with the new
JQL service. Therefore, we’re replacing them with compatible ones.
We’re deprecating the following Jira Platform REST endpoints:
* GET /rest/api/3/search - Search for issues using JQL (GET)
* POST /rest/api/3/search - Search for issues using JQL (POST)
* POST /rest/api/3/search/id - Search issue IDs using JQL
* POST /rest/api/3/expression/eval - Evaluate Jira expression
There is a deprecation period of 6 months, and these endpoints will be removed
after May 1, 2025.
For a list of replacement endpoints, and other information, view the Atlassian
Developer Changelog.
BUSINESS PROJECTS SHARED CALENDAR
ROLLING OUT NEW THIS WEEK
Announcing three improvements to the calendar view experience in business
projects.
We’re improving the calendar view experience in business projects.
1. Bug Fixes
* Unschedule Work: You can unschedule work even if the schedule work panel is
empty.
* Summary Truncation: Summaries are no longer truncated.
2. Pagination
* We’ve introduced pagination for calendars with more than 50 items.
3. View settings button
* We’ve added a View Settings button making it easier to navigate, stay
informed and customize your view. Now you can:
* Quickly open Issues from the sidebar.
* Hide Done items.
* Show/Hide issue key.
* Show/Hide weekends.
* Choose week start day.
* Show software release rates.
FILTER FORM-RELATED REQUESTS IN JIRA
ROLLING OUT NEW THIS WEEK
You can now quickly filter and locate requests linked to a submitted form,
without the need to manually search.
To get started:
* Open Jira, and navigate your business project.
* Go to the Forms tab.
* Locate the recent form.
* Select View submitted.
You’ll be taken to your list view with the new search filter already applied.
EDIT THE NAME OR ICON OF A BUSINESS PROJECT
ROLLING OUT NEW THIS WEEK
You can now edit a business project’s name and icon directly in line, without
navigating to project settings. Simply select either the name or project from
anywhere in the project, make your updates, and confirm.
CREATE ACTION ITEMS IN JIRA ISSUES
ROLLING OUT NEW THIS WEEK
There may be times when you just want a simple to-do list instead of creating
subtasks within issues.
You can now add action items within the description and comments of an issue.
This feature lets you use checkboxes to format your text, helping you compile a
list of the things that don’t need separate tracking.
More about action items
To get started:
1. Navigate to a Jira issue.
2. In the Description field, select Action item (checkbox icon) from the
toolbar available in the editor or type [] (open and close square brackets).
3. Type you action.
BRAND YOUR JIRA PRODUCTS WITH A CUSTOM DOMAIN
ROLLING OUT
You can now use custom domains to brand your Jira products. Custom domains
provide easy-to-remember URLs for your users to access your products.
You can create a custom domain if you have a Jira Premium or Jira Service
Management Standard plan.
Previously, this feature was only available for Jira Service Management help
center. Tell me more about custom domains
To create a custom domain:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Products > Product URLs.
3. Select Add custom domain. This is only visible if you have an eligible
product.
4. Review the Before you add a custom domain page, and select Next.
5. Select which product you want to access from your custom domain.
6. Follow the prompts to specify your domain. You’ll need to enter two
subdomains and a domain.
7. Enter a Redirect URL. This is optional.
8. Review changes and select Create domain.
IT’S EASIER FOR PEOPLE WITH JIRA TO START USING JIRA PRODUCT DISCOVERY
ROLLING OUT
We know our products can be complicated. So now people who have Jira, and have
recently also added Jira Product Discovery, will see simple recommendations on
how to start using Jira Product Discovery. For example, inviting teammates,
using a template, etc.
That means it’s easier to know what to do first in Jira Product Discovery so
that you’re getting the most out of it.
The recommendations will show up in the ‘Your work’ part of Jira, and everyone
with either a Free, Standard, or Premium plan will see them. You can dismiss
them anytime so they stop showing up.
STREAMLINING GENERAL AND BLANK PROJECT TEMPLATES IN JIRA SERVICE MANAGEMENT
ROLLING OUT
We’re simplifying our Jira Service Management project templates and no longer
splitting out our general and blank templates by IT and business team types. Now
you’ll see just one general service management template and one blank template
to cater to all needs - no matter the team type.
These project templates will replace the previous general service management for
IT teams and general service management for business teams templates, and the
blank project for IT teams and blank project for business teams.
Use the general service management template if you wish to get up and running
with basic pre-configured settings to start managing incoming service requests,
whilst blank projects let you fully customize how you manage incoming service
requests.
Find out more about projects templates in Jira Service Management
IMPROVED SEARCH USING SUMMARY AND DESCRIPTION FIELDS
ROLLING OUT
We’re boosting performance in the issue navigator by changing how the search
field works behind the scenes. When using the search field, results will be
based on the Summary and Description fields.
Before this change, results were based on multiple text fields such as Summary,
Description, Comments, and any custom text fields, which caused results to be
slower to load.
If you’d prefer to search using text fields, select More + to view additional
field filters, then select Text.
To try it out, head to the issue navigator by going to your project, then select
Issues in the sidebar.
NEW WAYS TO EDIT CARD COVERS
ROLLING OUT
Now you can easily choose a color or an attachment, or upload a new card cover.
Select the action menu on the bottom right and choose "Edit cover"
WE'RE ADDING AN UPGRADE BUTTON FOR FREE CUSTOMERS
ROLLING OUT
In the top right of the navigation, you might see a new button that will help
you upgrade to a new plan when you get close to the user limit.
This button will help you understand how many users you have, what you get when
you upgrade, and how to upgrade.
GET NOTIFIED WHEN YOUR ISSUES TRANSITION TO ANOTHER STATUS
ROLLING OUT
In team-managed projects, users can now receive a separate email when an issue
transitions to a different status.
Previously, users in team-managed projects received the same email regardless of
whether an issue was edited or transitioned to another status.
Project admins can now enable a separate email to notify their team when an
issue is transitioned. This provides more granular control about email
notifications and reduces clutter for users who are only interested in issue
transitions.
To enable email notifications to users when an issue is transitioned:
1. From your project’s sidebar, select Project settings and then Notifications.
2. Select Add notification.
3. Using the dropdown, search for and select the issue event An issue is
updated by a workflow transition (generic event).
4. Select the users and roles that will receive this notification.
5. Select Add.
More about customizing notifications in team-managed projects
DISCOVER CONFLUENCE TEMPLATES WITHIN YOUR JIRA ISSUE
ROLLING OUT
If you’re using Jira and have recently added or been given access to Confluence,
you'll now see templates in certain issues. The templates will be for relevant
types of documents to your issues. For example:
Bug issue type = Known errors Confluence template
Story issue type = Product requirement Confluence template
Epic issue type = Project plan issue type
If you select one of these templates, you'll be able to create the page without
leaving Jira. It will then automatically be linked to your issue. After that,
you won’t see the templates in any Jira issue.
These templates will appear for up to 14 days after Confluence is first added to
your site, after which they'll disappear.
You can remove the templates from your Jira issues at any point using the more
actions menu on the placeholder itself.
QUICKLY VIEW IMAGES DIRECTLY FROM YOUR BOARD ISSUE CARDS
ROLLING OUT
By adding an image attachment to an issue, you can show or hide images directly
from your board in a company-managed software project.
To add or change an issue’s cover image:
1. Navigate to your board view.
2. Hover over an issue.
3. Select ••• (more) on the issue.
4. Select Edit cover image and choose from the options.
FORMS NOW SUPPORT CASCADING FIELDS
ROLLING OUT
There may be times when you want to surface only specific values to customers
that are dependent on another choice they've made. These could be on forms that
need to capture a customer’s address, for example. Instead of seeing all
possible cities or states, you can make it easier for customers by letting them
narrow down their options by selecting a country first.
This is possible with cascading fields. This new field type lets you create
conditional fields with two lists of values: a parent list of values and a child
list of values that are dependent on what is selected in the parent list.
Read more about using forms
NEW JIRA INSTANCES ARE NOW DOMAIN-ENABLED
ROLLING OUT
New Jira instances will be automatically domain-enabled from now on, meaning
anyone with your organization's email domain (the one you used to sign up) will
have access to projects that you send them links to. It'll save you time – you
won't need to grant them access, after you've invited them. (Excludes existing
Jira instances.) Find out how to disable this feature in your new Jira instance.
CREATE A BOARD MORE EASILY FOR YOUR COMPANY-MANAGED SOFTWARE PROJECT
ROLLING OUT
For those who are on our Early Access Program, we've streamlined the board
creation experience. You'll still be able to create a board for your
company-managed software projects directly from the sidebar navigation. Boards
can also be starred, allowing you to easily navigate to the areas where you most
often work.
Note: This is only for company-managed software projects and for customers who
have been selected to participate in the Early Access Program.
CHANGES TO THE COPY FOR CONFLUENCE LISTING IN APP SWITCHER
ROLLING OUT
The app switcher in your Atlassian products is used to switch between different
apps and products.
If you have Confluence, you will see it listed in the app switcher with a short
sentence about what it is and what you can use it for. This sentence disappears
after your first 15 days of having Confluence.
This sentence has been updated. It will now read: Confluence. Document
collaboration.
ADD AND DELETE TRANSITION RULES IN THE NEW WORKFLOW EDITOR
As we continue to improve workflows in Jira, we're working to add important
features from the old workflow designer to the new workflow editor. In this
release we've made approval-related transition rules visible in the sidebar when
you select a transition, and added the ability to add or delete those rules as
needed.
EDIT YOUR JIRA SUMMARY STRAIGHT FROM SMART LINK LIST VIEW
ROLLING OUT
This update to Smart Link list view allows you to edit the Jira summary without
the need to open the issue.
While viewing Jira issues in Smart Link list view, select the summary from one
of the items. Once the cursor appears, you can edit the summary straight from
the cell.
REMOVAL OF SEN FROM UPM MANAGE APPS
ROLLING OUT
The SEN field has now been removed from the Manage apps section of UPM. To
identify an entitlement, you'll have to use the new cloud identifier, which is
the Entitlement number.
IT'S EASIER FOR END USERS TO CONNECT THE RIGHT TYPE OF CONFLUENCE DOCS TO JIRA
ISSUES
COMING SOON
Jira issues have a field for Confluence content so that you can link important
documents to your tasks in Jira. Now, if you’re viewing a bug, story, or epic
issue, you may see a recommended Confluence template.
These templates are customized based on the issue type. For example, a ‘known
errors' template will appear in a bug issue.
Before, end users could only use these templates by sending a request for
Confluence to their admin. Now, end users on Free plans can access Confluence
and the templates straight away, without leaving Jira and without waiting for
request approval.
You can dismiss these template recommendations at any time.
REDUCING ‘ISSUE’ TERMINOLOGY IN JIRA
ROLLING OUT
We’re reducing the use of 'issue' terminology in an effort to simplify our
language and better suit all team types.
MORE TEXT FORMATTING FOR JIRA PARAGRAPH CUSTOM FIELDS
ROLLING OUT
With more edit options available in newly created paragraph custom fields, you
can style long-form text and links how you like. Now available for
company-managed projects.
To view this change to paragraph custom fields:
1. Create a new paragraph custom field in your Jira project.
2. Add the newly created paragraph field to any issue type in project settings.
3. Open any issue within the same issue type.
4. Select the newly created paragraph custom field from the issue, to view and
use the new edit experience.
SIMPLIFY YOUR MARKETING WORK INTAKE WITH A FORM TEMPLATE
ROLLING OUT
With a ready-to-go template, you can quickly request information from your
stakeholders for marketing campaigns, content creation, event planning, social
media posts, graphic design, or email marketing.
To get started:
1. Select Forms from the project view navigation.
2. Select Templates to open the templates drawer on the right.
Learn more about creating forms
ADMINS CAN NOW DELETE PREVIOUS PROJECT KEYS
ROLLING OUT
We’re giving admins the ability to delete previous project keys so they can be
used for new projects.
Whenever you change your project key, we automatically save your previous
project keys. This ensures any links, filters, and queries using your previous
key continue working.
Admins can now delete a previous project key from a project so it can be used
for a new project.
To delete a previous project key:
1. Select Project settings, then Details.
2. In the Previous project keys field, delete the relevant project key.
3. Select Save.
We recommend letting users know before you delete your previous project key so
that they can update any links, filters ,or queries using the previous project
key.
More about project keys
CUSTOM FIELDS AVAILABLE IN THE AUTOMATION SMART VALUES PANEL
ROLLING OUT
We're adding a new feature to the smart values panel in Jira and Confluence
automation. The panel will now have an additional filter called Custom fields,
which will contain up to 50 custom issue fields from the current instance you
have access to. You can search and copy these custom fields to use them while
creating rules in the rulebuilder. Custom fields can be filtered by either the
smart value or the untranslated name using text input. We will also display if
these fields can be used globally or are bound to a single project.
To start using this feature:
1. Open the automation rulebuilder.
2. Select a trigger for your rule.
3. Add an action that has smart value text fields, such as the Log action, Send
web request or Create issue action.
4. Select the {} button to open the smart values panel.
5. Select the Custom fields tab to browse available custom issue fields.
6. You can now copy and use these custom fields in your rule.
Learn more about using smart values in Atlassian automation
SMART LINKS ARE NOW AVAILABLE IN MORE FIELDS
ROLLING OUT
Add and view Smart Links in URL and short text fields. This will apply to your
issue, list, board, and backlog views.
From your list or issue view, copy a valid URL link into a URL or short text
field.
Read more about using Smart Links
SMART LINKS AVAILABLE IN MORE FIELDS
ROLLING OUT
Add and view Smart Links in URL and short text fields. This will apply to your
issue, list, board, and backlog views.
From your list or issue view, copy a valid URL link into a URL or short text
field.
NEW FILTERING OPTIONS IN YOUR BOARD
ROLLING OUT
In business projects, we're adding the ability to filter by parent issues in
your board. This will make it easier and simpler to filter by all associated
child issues.
From the board, select Filter, then scroll to find and select from your Parent
filter options.
HIGHLIGHTED SEARCH TERMS IN IN-PRODUCT HELP
COMING SOON
When you search in in-product help, we'll highlight your search terms in results
so you can quickly see how the results relate to the terms you've entered.
To search in in-product help, select the help (question mark) icon in the
navigation and enter your query in the search field.
Note: In-product help is available in many screens in Jira, including in
software, service desk, and work management projects. There may be some screens
where in-product help isn't available yet.
CREATE CUSTOM FIELDS WHILE BUILDING FORMS
ROLLING OUT
Admins in team-managed projects can now create custom fields within a form as
they're building the form, without having to go to project settings.
CUSTOMIZE DURATION FOR WAITING FOR A RESPONSE WHILE RUNNING THE AWS SSM DOCUMENT
AND RESUME RULE IN CASE OF NO RESPONSE
ROLLING OUT
When running the AWS SSM document, you can configure the action to wait for a
response for a duration of 1 to 15 minutes. Additionally, you can now set the
rule to resume even if AWS SSM doesn't return a response within the specified
time.
CUSTOMIZE DURATION FOR WAITING FOR A RESPONSE WHILE RUNNING A QUERY IN NEW RELIC
AND RESUME RULE IN CASE OF NO RESPONSE
ROLLING OUT
When running a query in New Relic, you can configure the action to wait for a
duration of 1 to 15 minutes. Additionally, you can now set the rule to resume
even if New Relic doesn't return a response within the specified time.
CUSTOMIZE DURATION FOR WAITING FOR A RESPONSE WHILE LAUNCHING A JOB TEMPLATE IN
ANSIBLE AND RESUME RULE IN CASE OF NO RESPONSE
ROLLING OUT
When launching a job template in Ansible, you can configure the action to wait
for a duration of 1 to 15 minutes. Additionally, you can now set the rule to
resume even if Ansible doesn't return a response within the specified time.
CUSTOMIZE DURATION FOR WAITING FOR A RESPONSE WHILE STARTING A RUNBOOK IN AZURE
AND RESUME RULE IN CASE OF NO RESPONSE
ROLLING OUT
When starting a runbook in Azure, you can configure the action to wait for a
duration of 1 to 15 minutes. Additionally, you can now set the rule to resume
even if Azure doesn't return a response within the specified time.
CUSTOMIZE DURATION FOR WAITING FOR A RESPONSE IN VIRTUAL MACHINE IN AZURE AND
RESUME RULE IN CASE OF NO RESPONSE
ROLLING OUT
When restarting Virtual Machine in Azure, you can configure the action to wait
for a duration of 1 to 15 minutes. Additionally, you can now set the rule to
resume even if Virtual Machine in Azure doesn't return a response within the
specified time.
UPDATES TO SERVICE PROJECT TEMPLATES
ROLLING OUT
We've made some changes to service management templates when creating a new
service project. Only new templates are affected by this change.
The IT service management template no longer includes problem management, change
management, and advanced incident management features. These features are now
found in the advanced IT service management template.
These changes are reflective of our updates to what's included in Jira Service
Management's Standard and Premium plans. Read more about updates to Jira Service
Management's pricing and packaging.
THE REQUESTS BETA FEATURE IS LEAVING SOON
ROLLING OUT
We’re removing the Requests beta feature on October 4, 2024. This feature was
intended to make it easy to view your Jira Service Management requests from your
Jira Software project, but we’ve found its performance wasn’t quite up to
scratch.
If you’ve participated in the Requests beta in your software project and have
been using it, all your request data will still be available in Jira Service
Management. You can still work with requests from your software request by
implementing one of the alternative options we’ve provided on Atlassian
Community.
EDIT YOUR HELP CENTER'S HOME PAGE LAYOUT AND ADD RICH CONTENT TO IT
ROLLING OUT
With this release, admins will have more control over their help center's home
page, allowing them to tailor it to fit the needs of their audiences. They will
be able to:
* hide and reorder sections on the home page to create a more organized
experience
* add layouts, images, and rich content to make the help center visually
engaging and user-friendly.
This will help admins create a more customized and appealing help center for
their different audiences.
NEST MEDIA AND CODEBLOCKS IN QUOTES
ROLLING OUT
We’ve added the capability to nest media (images, videos, etc.) and codeblocks
inside of quotes in the editor. This allows for better context when formatting
quotes.
* * Media in quotes*: Users can now embed images, videos, and other media types
within quotes, enhancing visual context.
* * Codeblocks in quotes*: Codeblocks can now be nested inside quotes, making
it easier to reference and highlight code snippets within discussions.
NEW AND UPDATED VIRTUAL AGENT CHANNEL MANAGEMENT
ROLLING OUT
This update simplifies channel management and enhances the visibility and usage
of the virtual agent across your Jira Service Management projects.
Streamlined configuration: For a more efficient admin experience, manage all
channel configurations from a single Jira Service Management channel home.
Centralized channel visibility: View all connected channels with the virtual
agent in one place.
Unified testing: Test draft intents and AI Answers directly from the web
preview, eliminating the need for specific Slack request channels.
Read more about how to use the virtual agent in your customer channels
A NEW HOME FOR HELP CENTER CUSTOMIZATION FEATURES
ROLLING OUT
Quickly access customization options for your help center. All customization
features related to the help center are have now moved under the Customize
button in the top navigation. From there, you can manage announcements, add
login page messages, customize the look and feel, manage topics and portals, and
edit the layout of your help center.
QUICKLY VIEW IMAGES DIRECTLY FROM YOUR BOARD ISSUE CARDS
ROLLING OUT
By adding an image attachment to an issue, you can show or hide images directly
from your board in a company-managed software project.
To add or change an issue’s cover image:
1. Navigate to your board view.
2. Hover over an issue.
3. Select ••• (more) on the issue.
4. Select Edit cover image and choose from the options.
SAY HELLO TO SMART REPLIES IN JIRA ISSUES
ROLLING OUT
Adding comments to issues has just become faster and easier. With the touch of a
button, you can add a pre-populated comment to an issue and instantly save it,
or use it as a starting point to type more information before saving.
NOTE: This feature is currently available on Free sites. If you'd like access to
it, contact Atlassian Support.
What’s the benefit of smart replies? Jira’s real superpower lies in
collaboration. By encouraging your team to respond to work and comment on issues
faster and more often, smart replies can help your team embrace Jira’s unlimited
power of accelerated collaboration.
If you don’t want to use a smart reply, simply start typing in the issue’s
comment box, and the smart replies will disappear.
To disable the feature, go to Settings > Personal Jira settings > General, and
disable the smart replies toggle within the Jira labs section. (This only
affects you.) Or to remove the feature entirely (affecting everyone in your Jira
instance), contact Atlassian Support.
Read more about smart replies.
SEARCH FOR BOARDS BY PROJECT
Filter boards by project to quickly find the exact board you’re looking for. To
try it out, go to Your work > Boards > View all boards. From there, you can
search for boards by both keywords and project.
INTRODUCING WEEKLY VIEW FOR THE JIRA SERVICE MANAGEMENT CALENDAR
ROLLING OUT
We’re excited to add the highly requested week view to Jira Service Management's
calendar alongside the existing monthly view of work. Now, you can plan, track,
and prioritize work with a focused view week by week, and schedule work items by
the hour for more granular control of your tasks and requests.
1. Go to Calendar in your service project's navigation.
2. Select the Month menu, and switch to Week.
3. View and schedule your work items on the calendar by week.
CHANGES TO WHEN THE PARENT FIELD CAN BE EDITED
ROLLING OUT
In Jira, administrators can configure screens for an issue operation (create,
view, and edit).
If a screen has been associated with the “Edit Issue” operation, only fields
added to this screen should be editable. However, the parent field previously
ignored the edit issue screen. If the parent field was not on the edit issue
screen, it was still considered editable. We are changing this behaviour to make
the parent field behave like other fields, and ensure it is not editable if the
parent field is not on the edit issue screen.
To avoid problems arising from the change in behaviour, the parent field will be
added to all existing screens configured for the edit issue operation.
When this change has rolled out, Jira administrators can remove the parent field
from the edit issue operation screen if they wish to restrict the editing of the
parent field.
COMPACT WAY TO SEE ALL LINKED ISSUES IN JIRA
ROLLING OUT
Instead of scrolling through a long list of linked issues, they’re now neatly
displayed in the Linked issues column.
When selected, a smaller window opens with linked issues sitting side-by-side.
Each is still hyperlinked so you can quickly refresh your memory, and a scroll
bar means you still have access to them all.
This saves on space and helps to reduce page load times too.
RECORD OR UPLOAD LOOM VIDEOS ON A JIRA ISSUE
ROLLING OUT
Users can now record Loom videos directly from the Jira issue view, or insert
existing Loom videos directly into a Jira issue, ticket description, or comment.
If Loom is not an active product on a site, attempting to record a Loom video in
the issue view will allow users to activate Loom, or send a request to activate
Loom to the site admin.
From the + Add menu in a Jira issue, select the Record a Loom video option to
record directly into the issue. These Loom videos will appear under a new Loom
video section in the Jira issue.
ADDING ADMIN CONTROLS FOR THE "HIDE UNUSED FIELDS" FEATURE IN JIRA
ROLLING OUT
We're responding to requests from admins who have requested to control the Hide
unused fields feature in Jira. So, we've added the ability to globally switch
the feature on or off.
To manage features on your site:
1. Go to Settings > System.
2. Select Edit Settings.
3. Scroll to Options and choose the settings you’d like to turn on or off
4. Select Update to save your changes.
COLLECT HIGHER QUALITY INFORMATION WITH BUSINESS FORMS
ROLLING OUT
Gather better quality information with new functionality for business forms.
Choose from more fields including parent, category and people. Have more control
by making fields optional or required to submit when building a form. You can
also add more detailed guidance for people submitting a form, by adding field
descriptions.
Manage your form fields
To find updates to business forms, you’ll need project admin access:
1. Open a business project and navigate to Forms in the project navigation.
2. Select an existing form or select + Create form
3. Find all new functionality while building your form.
USE AUTOMATION RULES TO ADD TEXT TO NEW PAGES
ROLLING OUT
The Publish new page automation component now supports adding text to the body
of the page. We're adding an additional field that allows you to input content
that will be added to the page when it's created.
Add the Create page action to your automation rule and input your custom text in
the Page content field.
CONNECT YOUR CODING TOOLS WITH EASE
ROLLING OUT
It's now easier than ever to connect your source code management tools to your
software projects. GitHub, GitLab, Bitbucket? Too easy – the options are
practically endless. Minimize context switching, know the exact development
status of work, and more.
COLLECT WORK REQUESTS WITH FORMS FOR ALL JIRA PROJECTS
ROLLING OUT
Collect work requests from stakeholders directly into all Jira projects. Once
someone completes your form, this creates an issue ready to be prioritised and
worked on straight away.
To create a Jira form, you’ll need project admin access:
1. Open a project, and navigate to Forms in the project navigation.
2. Select an existing form, or select + Create form.
How to create a form.
AN IMPROVEMENT TO THE JIRA SEARCH EXPERIENCE
ROLLING OUT
We’re boosting performance in the issue navigator by changing how the search
field works behind the scenes.
When using the search field, results will be based on the Summary, Description
and all text custom fields. The Search issues field in the top navigation will
also follow this rule.
Before this change, results were also based in Comments and Worklog, which
caused results to be slower to load.
If you’d prefer to search using text fields, select More + to view additional
field filters, then select Text.
To try it out, go to the issue navigator in your project and select Issues.
VIEW AND FILTER VIRTUAL SERVICE AGENT CONVERSATIONS BY CHANNEL
ROLLING OUT
On the Conversations page in the virtual service agent, you can now see
conversations from all of your connected channels (instead of just Slack).
We've added a Channel column so you can see the source channel at a glance, as
well as a filter to narrow down conversations by channel.
Read more about using conversation data to improve your virtual service agent's
performance
UPDATE STORY POINTS DIRECTLY IN THE ISSUE NAVIGATOR LIST VIEW
ROLLING OUT
You can now edit the Story points and Story point estimate fields directly in
the list view of the issue navigator.
1. Go to Issues in the project sidebar
2. Switch to List view
3. Find the Story points or Story points estimate columns and update them
without opening the issue
EDIT YOUR HELP CENTER'S HOME PAGE LAYOUT AND ADD RICH CONTENT TO IT
ROLLING OUT
With this release, admins will have more control over their help center's home
page, allowing them to tailor it to fit the needs of their audiences. They will
be able to:
* hide and reorder sections on the home page to create a more organized
experience
* add layouts, images, and rich content to make the help center visually
engaging and user-friendly.
This will help admins create a more customized and appealing help center for
their different audiences.
WE’VE CLEANED UP YOUR JIRA BACKLOG
ROLLING OUT
Only view the issues that need doing from your backlog. We’re now automatically
filtering out any issues if they have a done status or a resolution.
To view this change to your backlog, you'll need to be using a team-managed
software project with sprints enabled:
1. In your project navigation, open your Backlog.
2. View your list of issues in your backlog. This should no longer include
issues with a status category of done.
To view done issues, navigate to other views such as the board or list.
CREATE EMBEDDED RELEASE NOTES WITH A CONFLUENCE TEMPLATE
ROLLING OUT
You can now create release notes in an embedded Confluence page using our
improved release notes template.
When you start the release process, you can create release notes in a Confluence
page. Select the issue types and Jira fields you want to add to the template.
The release notes will open in a new Confluence page that you can edit and
share.
WE'RE UPDATING THE ICON USED IN TRIAL BUTTONS
When you're in a trial, you'll see a button at the top left of your Atlassian
product that states the number of days you have left in your trial or states
what plan you are trialing. Before, the icon next to it depicted sparkles. Now,
that icon will depict a gem.
Whenever you see a gem icon, you can expect that button or information is
related to a trial of a paid plan (Standard or Premium).
You'll see this change when you are in a trial in the trial button in the top
right of your screen.
HIDE UNUSED FIELDS WHEN CREATING ISSUES
ROLLING OUT
There can be a lot of fields to scroll through when you’re creating issues, and
we know there are many fields that are simply unused.
We’re introducing a feature that only brings up the fields you actually use.
We’ll create a personalized Create issue form for each issue type and project.
All the fields you don’t use will be hidden in a More fields section, so you'll
always be able to interact with them. The feature is continuously learning. If
we notice you using a previously unused field, we’ll pull it out of the More
fields section for the next time.
We’ll automatically turn on the feature to hide unused fields when creating
issues, but you can manage it by heading to Personal settings and finding to the
Jira labs section. From there, you can use the toggle to opt in and out of the
feature.
EFFICIENCY IMPROVEMENTS IN THE CALENDAR VIEW
ROLLING OUT
In our ongoing effort to streamline tasks and enhance your experience with the
calendar view, we’re rolling out the following improvements:
• Load more issues without pagination — We’ve replaced the page numbers at the
bottom of the calendar with a single Load more button. Selecting this will keep
currently loaded issues in view while loading the next 50.
• Real-time updates — If you create, update, or delete an issue, other team
members viewing the calendar will see those changes in real-time without
reloading the page.
• Hide done items via URL — If you switch on the toggle to hide done items, the
parameter hideDone=true will be added to the page’s URL. If switched off, the
parameter will be removed. You can use these URLs to share exactly what you’re
seeing, without unnecessary configuration. This change is only applicable to
business projects.
• Manage issue types — While creating issues in the calendar, you’ll notice a
new option to Manage types in the issue type dropdown. Selecting this gives you
quicker access to the issue type configuration page in project settings. This
change is only applicable to software projects (to match existing functionality
in business projects).
• Improved sorting — When a day in the calendar contains multiple items, you’ll
notice a consistent sorting pattern that better shows the continuity of longer
events and prioritises important context like sprints and releases. Sprints will
always appear at the top of the day, followed by multi-day events, releases, and
single-day events.
Unless otherwise stated, these changes will be available on software projects,
business projects, plans, and Jira Service Management.
To try out these improvements, head to the calendar by going to your project,
then select Calendar in the sidebar.
CLEAR DATE AND TIME FILTERS IN THE AUTOMATION AUDIT LOG
ROLLING OUT
We're introducing a new feature to Jira and Confluence automation that allows
you to clear all selected filters in the audit log with a click of a button.
This change will help you to save time and improve efficiency, as you'll no
longer need to manually de-select all the selected filters yourself.
To start using this feature:
* Open the audit log in either Jira or Confluence automation.
* Apply any desired date and time filters to the audit log.
* Once you are done with these filters, select the Date and time button.
* Select Clear filter. All selected date and time filters will automatically be
de-selected.
* Your audit log will now have no date and time filters applied to it.
Learn more about using the audit log in Jira and Confluence automation
JIRA
NEW RESTRICTIONS IN THE NEW WORKFLOW EDITOR EXPERIENCE
ROLLING OUT NEW THIS WEEK
We've added two more transition rules to the New workflow editor experience.
Prior to this change, these rules only existed in the old workflow editor.
GET WORK SUGGESTIONS FOR PULL REQUESTS WITH NEW COMMENTS
ROLLING OUT NEW THIS WEEK
You’ll now get work suggestions in Jira when new comments are added to your open
pull request since the last time you got this suggestion for the same pull
request. When you select your avatar on the board, any available suggestions
will automatically appear on the work suggestions panel.
The availability of this suggestion type depends on the source code management
tool you’re using and its connection with Jira. The new suggestions will be
available in scrum and kanban projects in Jira.
Read more about work suggestions in Jira
USE THE GITHUB FOR JIRA APP TO CONNECT GITHUB ENTERPRISE, INSTEAD OF DVCS
Jira admins making a new GitHub connection for a new organisation now need to
install the GitHub for Jira app. The app functions just like the DVCS Connector,
but with better security features and improved performance.
This only applies to new GitHub connections in new organisations. Existing
connections using DVCS are not affected.
Learn more about the GitHub for Jira app.
CONTROL WHAT YOU SEE IN YOUR PRODUCTS
ROLLING OUT
Product recommendations now have controls, so now you can dismiss them or learn
more about why you’re seeing them. These controls are being added to the
recommendations in the app switcher menu which means you'll have more control
and receive better product recommendations.
You can select the three dots next to the recommendation to learn why we have
recommended it or to dismiss it entirely.
The recommendation controls will first be released to both Free and Standard
teams of up to 50 users. Note: Only admins will be able to add a new product by
clicking on the recommendation.
ORGANIZE AND TRACK WORK AGAINST COMPASS SOFTWARE COMPONENTS
ROLLING OUT
You can now link issues to Compass components from any company-managed Jira
Software project.
This helps your team organize and track work in Jira against elements of your
software architecture cataloged in Compass – so you can understand the impact of
that work; prioritize work more effectively; and find the information you need
to get that work done faster.
Learn more about Compass components
Switch to Compass components (project admins)
1. In your project sidebar, select Components.
2. Check that Compass components are turned on. Next to Create component, it
should say Compass components. If it says Jira components, select it and
switch to Compass components.
* Jira components won't be deleted, and they'll still be visible on issues
they were previously linked to. You can switch back to Jira components at
any time.
Read the full documentation
Link issues to Compass components
If you don't have Compass yet:
1. On the Components page, select Get Compass free. It'll take a couple of
minutes to set up.
* Only site admins can do this; if you're not a site admin, you can send a
request to your site admin to get Compass.
If you have Compass, but don't have any software components:
1. On the Components page, select Create component. Compass will open in a new
tab.
2. Fill out the information for the new component, including the name, type,
owner team, and related source code repository link. Read more about
creating Compass components
3. Open any issue in your project.
4. Select the Components field, and choose the Compass component you want to
link to the issue.
5. The component and its linked issue will appear on your project's Components
page; and you can search for the component in the backlog, boards, and issue
navigator.
If you have Compass, and have software components:
1. Open any issue in your project.
2. Select the Components field, and choose the Compass component you want to
link to the issue.
3. The component and its linked issue will appear on your project's Components
page; and you can search for the component in the backlog, boards, and issue
navigator.
Read the full documentation
COLOURFUL CATEGORIES
ROLLING OUT
Project admins can now assign colours to categories from the list view in Jira.
TRACK AND TRIAGE INCIDENTS AFFECTING YOUR SERVICES IN JIRA
ROLLING OUT
We’re excited to roll out the new incidents feature in Jira Software Cloud.
This feature pulls in data from connected incident management, monitoring, and
observability tools, so your development team can have a holistic view of
incidents impacting services they are responsible for.
Our first supported product is Jira Service Management, and we plan to add
support for more incident management and observability tools soon.
By turning unexpected incidents into manageable, visible work, you can improve
your team’s focus on quick resolution and internal review while building
proactive work practices to prevent incidents from happening again.
To get started with the incidents feature:
For some customers who use Jira Service Management, the feature will be
available and automatically appear under Operations in the list of features.
To turn it on manually:
1. Go to Project settings > Features.
2. Toggle Incidents on.
We're gradually rolling out the incidents feature over the next few weeks to
specific customers. If you don't see it yet, check back again soon.
GET SUGGESTIONS FOR CHILD ISSUES FROM AI
ROLLING OUT
Use Atlassian Intelligence to generate a list of suggested child issues, based
on the details of the parent issue.
When you accept a suggestion, a new child issue will be created and linked to
the parent issue.
To see a list of AI-generated suggestions:
1. Open the parent issue.
2. Select Add a child issue under the issue summary. If you are in a
company-managed project and want to create a subtask, select Create subtask.
3. Select Suggest issues.
We’ll then create a list of suggested child issues which you can accept, edit,
or decline.
TEMPLATE BUNDLES IN THE PROJECT CREATE PAGE
ROLLING OUT
Effortlessly create between 2 to 6 projects at once, with bundles. We're helping
streamline your project creation process and minimizing the need for repetitive
manual tasks. Whether you're working in Jira or Jira Service Management, bundles
guarantee a smooth project creation experience.
Choose from two pre-set bundles: the Marketing or the IT team bundle. And if
they don't fit your requirements, you have the flexibility to customize and
create your own bundle.
There are a few ways you can create a bundle, one way is to:
1. Select the plus icon + in the project sidebar
2. Choose More templates from the dropdown
3. Select Bundles
Another way to create a bundle is to:
1. Select Projects > Create project in the top navigation bar
2. Select Bundles
COMPANY-MANAGED PROJECTS: CREATE, EDIT, AND DELETE COLUMNS DIRECTLY ON THE BOARD
ROLLING OUT
If you want to quickly add or update a column on your board, you don’t need to
go far. You can now create, rename, move, set constraints for, and delete
columns without leaving the board. You’ll still have the ability to do all of
the above in your board’s settings page, but if you’ve only got time for a quick
fix, we’ve now got you covered!
If you’re a project or board admin for the board you want to update, you can try
the following changes:
* To create a column, select the + icon to the right of all columns.
* To rename a column, select its name to edit directly.
* To move a column, select its top, then drag the column to its new position.
* To set column constraints, right-click its name or hover to select more
actions (•••) > Set column limit.
* To delete a column, right-click its name or hover to select more actions
(•••) > Delete.
IMPROVED EDITING EXPERIENCE FOR QUEUES
ROLLING OUT
We've made improvements to the "Basic" editing experience for Queues in Jira
Service Management. The update includes improved dropdown fields and the ability
to select multiple options for ordering your queue.
VIEW HIGH-LEVEL WORK ACROSS MULTIPLE TEAMS WITH A NEW TEMPLATE
ROLLING OUT
Use the new cross-team planning template to get a high-level view of work across
multiple teams.
CREATE CONFLUENCE WHITEBOARDS DIRECTLY FROM YOUR JIRA BACKLOG
ROLLING OUT
With Confluence whiteboards, you can plan freely and execute quickly. Create a
whiteboard directly from your Jira backlog, copy backlog issues to the
whiteboard, and plan however you want.
Here are some suggestions for things you can do with Confluence whiteboards:
* Use award-winning templates such as a prioritizing and planning matrix
* Import Jira issues directly into your new planning whiteboard
* Link sticky notes and issues to show dependencies and timelines
* Turn sticky notes into Jira issues
* Engage teammates with real-time, group editing
* Collaborate using stamps, timers, and more
If an admin has three or more issues in their backlog, they'll see the button
that allows them to add Confluence and start using a whiteboard. Once a team has
Confluence, anyone with access to Confluence — including admins and end users —
will see the button on their backlog that allows them to create a whiteboard.
You can remove this button anytime by turning off all product recommendations at
in your Jira settings. Note: if you add Confluence and then turn off product
recommendations, you will lose this button.
MANAGE EMAIL NOTIFICATIONS BASED ON YOUR ROLE
ROLLING OUT
Due to popular demand, we’re bringing back the ability to manage emails in Jira
based on whether you’re a reporter or assignee for an issue.
These changes are being rolled out, so don’t worry if you can’t see them yet -
they’ll be there soon!
To manage email notifications based on your role:
1. Select Settings > Personal settings.
2. Select Projects and issues.
3. Turn on the toggle to the right of Send emails for issue activity.
4. Select when you’d like to receive emails for issue activity.
SITE OPTIMIZER NOW ARCHIVES PROJECTS
ROLLING OUT
You've heard of the Site optimizer (if you haven't, here's some reading you'll
love); now we've made it better. It now allows you to clean out old projects as
well as issues, project role permissions, and custom fields.
When looking at projects that can be deleted, you can select projects to clear
out from your site based on those that:
* have no issues or
* haven't been updated in a certain amount of time
From here, you can choose to either archive them or send them to the trash.
ACCESSIBILITY IMPROVEMENTS IN THE PROJECT TIMELINE
ROLLING OUT
Over the next few weeks, we'll be shipping a few accessibility improvements when
viewing the project timeline. These changes make it easier for those using
assistive technologies (such as screen readers) to track their work using the
timeline view.
BOARD AND BACKLOG INSIGHTS NOW AVAILABLE TO ALL JIRA USERS
ROLLING OUT
We’ve updated the Insights feature on the board and the backlog for
company-managed projects in Jira. Now, all users can view insights, regardless
of what permissions they have.
With real-time data, you can use insights to review your team’s progress,
identify issues that need attention, and plan your sprints with confidence.
Adjust, maintain, or refocus your priorities to keep the team on track.
Read more about insights in Jira Cloud
To view your insights:
1. Find your team's Jira software project.
2. Select the board or backlog.
3. Select Insights.
BULK DUPLICATE AND DELETE COMPONENTS IN THE AUTOMATION RULEBUILDER
ROLLING OUT
We're introducing a new feature that allows you to select multiple components at
once in the automation rulebuilder and either duplicate or delete them. This
change affects both Jira and Confluence, and should help to improve efficiency
in the rulebuilder, as you'll no longer need to select each component one at a
time to edit them.
To select and edit multiple components at once:
1. Hold down the Ctrl / Command key and click the left button on your mouse or
touchpad.
2. Select the number of components you want to duplicate or delete.
3. Once the components are selected, you can use the new menu to duplicate or
delete them.
SAVE AUTOMATION RULES IN A DISABLED STATE
ROLLING OUT
We're introducing a new feature that allows you to save automation rules in a
disabled state, which means they are draft rules that you can come back to edit
and turn on later. Previously, rules couldn't be saved as drafts and had to be
turned on immediately after creation. This new feature provides more freedom for
users and allows you to more effectively edit and refine your rules before
turning them on.
To get started with this change:
1. Open either Jira or Confluence automation.
2. Select Create rule and create your desired rule in the rulebuilder.
3. Click on the dropdown arrow next to the Turn on rule button.
4. Select Save rule without enabling.
5. You'll now be able to see the draft rule under your Rules list in
automation. It will appear as 'Disabled'.
6. When you're ready to turn on the rule, move the Enabled toggle to the right
so a tick appears.
7. Your rule is now turned on and ready to use.
JIRA PLANS: CHANGE PLAN OWNER
ROLLING OUT
You can now change who is listed as the owner of a plan in Jira, so you'll
always know who's in the driver's seat.
IMPROVEMENTS TO THE WORKFLOW EDITOR
ROLLING OUT
We've updated the workflow diagram in company-managed projects to be faster and
more accessible.
CONNECT ISSUES TO GOALS IN YOUR JIRA LIST
ROLLING OUT
Use the Goals field in Jira to connect your team’s work to higher-level business
objectives. Goals help your team understand how their efforts drive impact and
help leaders manage dependencies and mitigate risk. All issue types can now be
linked to a goal in software projects, business projects, and plans.
Enable the Goals field to show as a column in your list. Once enabled, you can
create goals, link issues to the goals they contribute to, and filter issues in
your list based on goals.
How to link and unlink goals to issues
PLAN TIMELINE HEADER ISSUE CREATE IMPROVEMENT
ROLLING OUT
You can now create issue types directly on your plan timeline without hunting
through the work hierarchy level.
From the Timeline header create button, you'll be prompted to select a project,
which will then display all possible child issue types. Save time and start
creating new work inside your plan with less hassle.
NEW RULES COMING TO THE NEW WORKFLOW EDITOR
ROLLING OUT
In the new workflow editor, you will soon be able to use the following rules:
* Set issue security level
* Validate that an issue has a specific status
* Restrict which users can transition issues between statuses
All of these were available in the old workflow editor before, but now you can
also use them in the new workflow editor.
NEW WORKFLOW EDITOR: TRIGGER A WEBHOOK RULE
ROLLING OUT
Connect Jira to other tools with the Trigger a webhook rule. By adding it to a
transition in the new workflow editor, you’ll be able to send a webhook and
notify an external system when an issue moves through that transition. This
allows your other tools to act on this updated information accordingly.
IMPROVED PERFORMANCE AND RELIABILITY FOR CSV EXPORTS
ROLLING OUT
If you need to export your Jira issues, you’ll notice a faster and smoother
experience due to the following improvements:
* Speed and reliability — the export process is faster and can handle a large
number of fields and extensive data sets
* Tracking and control — you can monitor the progress of your export, and
cancel if needed
To try it out, go to the Issues page in your project. Select Export, then select
a CSV export option.
Note that only one CSV export can be processed at a time.
NEW VALIDATION FOR FIELDS IN THE WORKFLOW EDITOR
ROLLING OUT
We've revamped how field validation works when building workflows for
company-managed projects, as well as introduced this feature to team-managed
projects.
When building a project workflow, validators let you specify criteria for when
an issue can move through a particular transition.
Go to Project settings > Workflow to get started, then follow these instructions
to add validators depending on your project type:
* Add or edit rule to a team-managed project
* Add or edit a rule for a company-managed project
If you're already using validators for a company-managed project, don't worry,
your existing rules still work and are fully compatible with the new experience.
MAINTAIN APPROVAL HISTORY WHEN BYPASSING APPROVALS
ROLLING OUT
This change allows users to bypass approvals while preserving approval data,
preventing data loss and improving history tracking.
During an approval state of a workflow, an issue can't transition to the
approved or declined status until all approval decisions are finalized.
However, transitions other than ‘Approve’ or ‘Decline’ can be used to manually
transition issues and bypass the approval state. Previously, if you transitioned
an issue’s approval state to a status other than ‘Approve’ or ‘Decline’, it
deleted the approval along with any recorded approver decisions from the
database.
As part of this change:
* if an issue’s approval state is transitioned to a status other than ‘Approve’
or ‘Decline’, it will be recorded as a ‘canceled approval’
* we preserve any active approvals (including approver decisions) that exist
for an approval state when an approval state has been bypassed
* all approvals data will be retained in the approvals activity history
* JQL queries will return issues with approvals activity, even if the approval
is canceled.
Tip: To ensure your approval state status and approver decisions are clearly
conveyed to your customers in the portal activity log, check how your workflow
statuses will appear to customers in the portal based on the display names
assigned to each workflow status.
1. From your project settings, go to Request types.
2. Select the name of the request type you want to modify, then select the
Workflow statuses tab.
3. Review and update the Status name to show customer for each workflow status.
SPEED UP YOUR NEXT JIRA IMPORT WITH CONFIGURATION FILES
ROLLING OUT
When importing multiple projects using CSV files, a configuration file can help
you save your preferences, such as project settings, Jira fields, and user
information, and use it for future imports. In the new import experience, select
Download a configuration file at the end of your next Jira project import.
Upload it with a CSV file in another import to bring in the same preferences
without the hassle of selecting the same fields once again.
To use a configuration file during an import:
1. From the navigation bar, select Projects > Create project > Import data.
2. Select the app from which you’d like to import your data from. If you can’t
find your app in the list, select CSV to use any CSV file to import your
data.
* If you select Asana, ClickUp, monday, or Trello, you can directly import
data without a CSV file.
3. Select Upload a configuration file (optional) and upload the configuration
file you downloaded from a previous import.
4. Select Next and continue with the import.
Read about configuration files
PRIORITIES PAGE REFRESHED AND MORE ACCESSIBLE
ROLLING OUT
Adding priorities to work communicates urgency and brings focus to the most
important tasks.
Use the refreshed Priorities page to add, delete, and re-order priorities. You
can also add priority names and colors and upload icons.
To see the list of priorities on your Jira site, go to Jira settings, then
issues, then priorities.
NEW BUSINESS PROJECT TEMPLATES WITH APPROVALS SET UP
ROLLING OUT
We've created and added four new templates with approvals already set up so you
can get started as quickly as possible.
If you're working on a project that requires approvals, consider using one of
the following templates to get you started:
* Manage approvals for your business project
* Manage approvals for documents
* Get approval for your budget
* Manage approvals for your campaign
Using these templates will help you save time in setting up and customizing your
own approvals process in your project.
INTRODUCING A BRAND NEW TOOLBAR FOR BULK ACTIONS
ROLLING OUT
We’re introducing a toolbar in the backlog so users can update multiple issues
even more seamlessly.
To use the new toolbar:
1. Select multiple issues from the backlog or list. You can either:
1. use the issue checkboxes
2. hold Ctrl (Windows) or Command (Mac) while selecting issues
3. hold the Shift key to select a group of adjacent issues
2. The new toolbar will appear. You can either select Edit fields to make edits
to fields in your issues or Change status to transition your issues.
PLANS IN JIRA - CHANGE THE DURATION OF THE PROGRAM BOARD
ROLLING OUT
We're a few months into the Program board Open Beta, and we've gotten a lot of
feedback about how to improve it. One of the most requested improvements was the
ability to change the number of sprints shown on the board and the duration of
them.
Guess what we're releasing today?
That's right: when you create a new Program board, you can now change:
* the duration of each column to between one and four weeks
* the total number of columns to show between four and 13
Using these, you can adjust the total duration of your board to be as little as
seven weeks and as much as 16.
Haven't met the Program board yet? Allow me to introduce you.
CREATE ISSUES DIRECTLY IN YOUR CALENDAR
ROLLING OUT
With just a few clicks, you can create and schedule issues directly in your
calendar.
Prior to this change, issues were scheduled by adding start and due dates or
using the unscheduled work panel. Issues can still be scheduled in those ways,
but this is now the quickest way to do it.
How to create, edit, and delete issues in your calendar
To create an issue in your calendar:
1. Select an empty space on the date you’d like the issue scheduled. The date
selected will be the issue’s due date.
2. Enter a summary, select the issue type, then select Create.
To create an issue that spans multiple days:
1. Click and drag to select multiple days. The first and last dates selected
will be the issue’s start and due date.
2. Enter a summary, select the issue type, then select Create.
ADD EXTERNAL SPRINTS TO YOUR PLAN
ROLLING OUT
You can now assign issues to any sprint in your site regardless of whether it's
included in your plan. This allows planners to assign work that belongs to teams
outside their plan without leaving the page. Your plan refers to these as
external sprints, and adds the EXT. lozenge next to their name.
External sprints are not added to your plan when you assign issues to them. To
use the more complex sprint-based planning capabilities such as capacity
planning, you'll need to add the board in which that sprint was created as an
issue source of your plan.
INSIGHT SETTINGS ARE BEING REMOVED FROM SOFTWARE PROJECTS
ROLLING OUT
As part of our ongoing effort to simplify project settings for admins, we're
removing the option to configure insight settings in Jira software projects.
Insights will continue to show as normal, but board admins and project admins
won't be able to enable or disable specific insights, and any insights that were
previously disabled will now be enabled. This means that all insights available
in a project will be visible to any user who selects Insights from the board or
backlog.
To send us feedback about this change:
1. In your Jira software project, select Board or Backlog.
2. Select Insights.
3. Scroll to the bottom of your Insights and select Give feedback.
COMPANY-MANAGED PROJECTS: FIXED BUG FOR ATTACHMENTS IN PRIVATE COMMENTS
ROLLING OUT
We've fixed a bug where attachments in private comments were visible to all
users. If your issue cards were configured to show images, these would show on
the board and backlog too.
This is no longer the case — if you can see attachments in private comments or
images on the board and backlog, rest assured that you're the intended audience.
QUICK-ADD BUTTONS DECLUTTERED IN THE ISSUE VIEW
ROLLING OUT
We’ve consolidated all the quick-add buttons to declutter the issue view,
enhance clarity, and scale. You’ll now find buttons, such as "Attach” and
“Linked issues”, under the Add button, and buttons from your third-party
integrations under Apps.
Read more about the changes
GET NEW WORK SUGGESTIONS FOR PULL REQUESTS NEEDING ATTENTION
ROLLING OUT
Work suggestions in Jira will now show you new suggestions for pull requests
that need your attention.
You’ll see suggestions when your pull requests are ready to merge, have been
inactive for more than five days, or when someone adds you as a reviewer on
their draft pull requests.
Depending on the source code management tool you’re using and its connection
with Jira, you may receive some or all of these work suggestions.
When you select your avatar on the board, these suggestions, if available, will
automatically appear in the work suggestions panel.
The new suggestions will be available in scrum and kanban projects in Jira.
Read more about work suggestions in Jira
CUSTOM COMPASS COMPONENT TYPES SUPPORT IN JIRA
ROLLING OUT
We're introducing a new capability in Compass that allows product admins to
create component types based on the terminology their teams use to categorize
them. Custom type names will be supported in Jira, but will use the OTHER icon.
In Compass, product admins can create up to 14 component types, but anyone on
their Compass plan can use them. This customization helps software teams better
group components at a high level across their distributed architecture.
CONNECT ISSUES TO HIGHER-LEVEL GOALS IN THE ISSUE VIEW
ROLLING OUT
You can now align your team’s work to higher-level goals directly in the issue
view. Goals help your team understand how their efforts drive impact and help
leaders manage dependencies and mitigate risk.
If you linked an issue to a goal before this change, the Goals field will be
automatically enabled in the issue view. This change will replace the previous
experience of connecting goals in the issue view.
If you haven’t linked an issue to a goal before, you’ll need to enable the Goals
field for an issue type.
To enable the Goals field:
* Open an issue of the type you'd like to add the Goals field to.
* Select Configure at the bottom-right of the issue (near the created and
updated dates).
* In the Fields panel, search for Goals.
* Drag the Goals field to the Context fields section.
* Select Save changes to finalize.
UPDATE TO EXCLUSION RULES IN JIRA PLANS
ROLLING OUT
We’re making tweak to the way our exclusion rules apply in Jira plans.
Previously, if a parent issue was excluded from a plan timeline, but the child
issue was visible, then the parent issue would still show based on “parent
completion.”
From now on, the exclusion rule will apply regardless of the completion status
of a parent and simply exclude based on the specific exclusion rule.
This unifies exclusion rule behaviour across plans.
UPDATES TO CREATING LINKED ISSUES FOR BUSINESS PROJECTS
COMING SOON
We’ve made some changes to the way you create linked issues in business
projects.
CREATE A CHILD ISSUE FROM YOUR PLAN TIMELINE
ROLLING OUT
You can now create a child issue type directly on your plan timeline without
hunting through the work hierarchy level. Using the inline menu above the issue,
you'll be prompted to select a project, which will then display all possible
child issue types. Save time and start creating new work inside your plan with
less hassle.
NEW ADDITIONS TO THE MORE (•••) MENU ON AN ISSUE
ROLLING OUT
When viewing the timeline in business projects, you can now change parent issue,
edit an issue's start and end dates, and link to to issues using the More (•••)
menu on the issue.
YOUR PROGRAM BOARD IN PLANS NOW RECOMMENDS SPRINTS
ROLLING OUT
When you sync sprints in your Program board, you'll now see recommended sprints
that align with the dates of the columns.
PLANS GROUP NOW DISPLAYS RELATED CHILD WORK ITEMS
ROLLING OUT
When grouping, child issues will now appear under their parent’s group,
regardless of their assigned group. This change to the plan timeline behaviour
aligns with the list view and project timeline.
CREATE ISSUES FASTER BY HIDING UNUSED FIELDS
ROLLING OUT
Creating issues in Jira is now easier and faster with the ability to focus on
the fields you use the most. We’ve added a new setting that lets you quickly
hide any fields you haven’t used in the past 30 days. This only updates your
personal settings, so it won’t affect anyone else on your team.
To try it out:
* Select Create to create a new issue in Jira.
* Select More actions (•••), then select the toggle next to Hide unused fields
to turn the feature on or off.
CREATE GOOGLE DOCS IN YOUR GOOGLE DRIVE WITH JIRA AND CONFLUENCE AUTOMATION
ROLLING OUT
We’re introducing a new component to Jira and Confluence automation that allows
you to create a Google Doc in your Google Drive by simply executing a rule. This
feature will help you to create Google Docs more quickly and easily, as you’ll
no longer need to create them manually - Atlassian automation can do it for you!
To get started with this change:
1. Navigate to the automation rule builder in Jira or Confluence.
2. Select a trigger for your rule.
3. Select the Create Doc in Google Drive action and add it to your rule.
4. Select a Google Drive folder for your Google Doc to be placed in. Your Doc
will be placed in your My Drive folder if you don't have permission to
select a location for it.
5. Add a title and any body content you want your Google Doc to contain.
6. Add any other desired components to your rule.
7. Once you've edited and finalized your rule, turn it on.
8. Your rule is now ready to go.
JIRA SERVICE MANAGEMENT
Jira Service Desk is now Jira Service Management! We’re in the process of
rolling out some exciting new features for all users. Learn more about these new
features.
DEDICATED PAGE FOR ATLASSIAN INTELLIGENCE ANSWERS IN THE VIRTUAL SERVICE AGENT
ROLLING OUT NEW THIS WEEK
We've moved the toggle for Atlassian Intelligence answers in the virtual service
agent out of the Settings page and into its own AI answers page.
To turn Atlassian Intelligence answers on or off in your project's virtual
service agent:
1. From your service project, select Project settings, then Channels & self
service, then Virtual service agent.
2. Select AI answers.
3. To activate Atlassian Intelligence answers, turn the toggle on next to
Atlassian Intelligence answers, and then select Activate.
* Atlassian Intelligence answers will start working immediately in all of
your connected channels.
4. To deactivate Atlassian Intelligence answers, turn the toggle off next to
Atlassian Intelligence answers, and then select Deactivate.
* Atlassian Intelligence answers will stop working immediately in all of
your channels.
Read more about Atlassian Intelligence answers.
NEW FIELDS IN THE VIRTUAL SERVICE AGENT'S 'SEND WEB REQUEST' STEP
ROLLING OUT NEW THIS WEEK
We've added new fields to the send web request step in the virtual service
agent!
The Request timeout (in seconds) field allows you to choose a specific timeout
(between 5 and 30 seconds) for web requests. In the event of a timeout, the
conversation continues down the ELSE branch.
The Response variable field lets you store web responses from send web request
steps, and then use them in send message and send web request steps later in a
conversation.
We've also added the ability to use Jira custom fields and system fields in the
send message step, using templating expressions that were previously only
accessible via web request variables.
Read more about creating a 'send web request' step in a virtual service agent
conversation flow.
USE THE GITHUB FOR JIRA APP TO CONNECT GITHUB ENTERPRISE, INSTEAD OF DVCS
Jira admins making a new GitHub connection for a new organisation now need to
install the GitHub for Jira app. The app functions just like the DVCS Connector,
but with better security features and improved performance.
This only applies to new GitHub connections in new organisations. Existing
connections using DVCS are not affected.
Learn more about the GitHub for Jira app.
CONTROL WHAT YOU SEE IN YOUR PRODUCTS
ROLLING OUT
Product recommendations now have controls, so now you can dismiss them or learn
more about why you’re seeing them. These controls are being added to the
recommendations in the app switcher menu which means you'll have more control
and receive better product recommendations.
You can select the three dots next to the recommendation to learn why we have
recommended it or to dismiss it entirely.
The recommendation controls will first be released to both Free and Standard
teams of up to 50 users. Note: Only admins will be able to add a new product by
clicking on the recommendation.
CHAT IN SLACK: EMOJI SHORTCUTS ARE NOW POWERED BY JIRA AUTOMATION
ROLLING OUT
Emoji shortcuts, based off Halp’s legacy recipes, now use Jira automation’s
powerful no-code engine. With this change, admins can manage all automation
rules in one place and emoji reactions can be used to edit issues created by
Assist in Slack — all allowing for a simpler configuration experience.
If your projects have custom emoji rules, you have until June 4, 2024, to set up
similar ones in automation. After that date, the emoji shortcut feature in chat
settings will no longer function.
Find out more in our Community blog
Before you start setting up your new automation rules, keep in mind:
* The ticket emoji shortcut used to create issues isn’t affected by this
change, so you don’t need to set this up in automation.
* You need to set up the eyes emoji shortcut, which assigns agents to issues.
Tip: Use the template from the Emoji shortcuts tab in chat settings to
quickly set up this automation.
To set up emoji rules in automation:
1. From your project settings, select Automation.
2. Select Create rule.
3. Select Emoji reaction to Slack message as your trigger*.*
4. Select Turn on rule, name your rule, and then Turn on rule again to save.
To help test your new emoji rules, you can now turn off emoji shortcuts in chat
without deleting them:
1. Set up your emoji rule in automation.
2. From the Emoji shortcuts tab in chat settings, find the rule to turn off.
3. Use the toggle to turn off the rule.
4. Test to your satisfaction.
DATA LIMITS FOR OBJECT SCHEMAS IN ASSETS
ROLLING OUT
Assets in Jira Service Management is a database and so requires a combination of
good data modeling and a great deal of processing power to handle large amounts
of data. Here are recommendations for how to structure your data for Assets
schemas.
See also: How to build an effective ITAM schema structure.
For this reason, we have introduced limitations on how many objects, attributes,
and attribute characters can be stored inside schemas within each individual
Assets in Jira Service Management site. Read more about how much data you can
store in Assets.
Exceeding these limits can cause performance and reliability issues, therefore
each site cannot create further items once they reach the limit. You can find
out how many objects your site currently contains using the feature usage
screen. Read more about how to track your usage.
IMPROVED EDITING EXPERIENCE FOR QUEUES
ROLLING OUT
We've made improvements to the "Basic" editing experience for Queues in Jira
Service Management. The update includes improved dropdown fields and the ability
to select multiple options for ordering your queue.
UPDATED PROJECT SETTINGS NAVIGATION IN JIRA SERVICE MANAGEMENT
ROLLING OUT
We've made some updates to the project settings navigation in Jira Service
Management. The new navigation makes it easier to scan and find what you’re
looking for, and aligns more closely with other Jira projects.
Related items are now in groups – considerably reducing the number of items
displayed upon landing in project settings. These groups can be expanded and
collapsed as required.
Labels have been updated for some items – giving a better indication of what to
expect on pages.
Layout and patterns are now consistent across Jira – meaning you'll have a
similar experience whether you’re using Jira or Jira Service Management.
NOW ACCESS SMART VALUES FOR FORMS AND FORM FIELDS
ROLLING OUT
Eliminate manual data entry and leverage dynamic data by accessing smart values
on submitted forms on issues. Not only can you now retrieve form data in Jira
Service Management, but can also use these values to power automations and fuel
reporting.
Access any submitted forms on an issue by using forms and the automation lists
smart values to format the value of forms in a list when setting up a rule. Plus
access any specific smart values of form fields and combine, reformat, and
manipulate values to suit your specific needs.
USE ATLASSIAN INTELLIGENCE TO DRAFT A REPLY
ROLLING OUT
You can now use Atlassian Intelligence to draft replies (beta) for your
customers. The replies will be based on comments added by agents while resolving
similar requests.
To use Atlassian Intelligence to draft a reply:
1. Select any issue from Queues.
2. Select Add internal note or Reply to customer.
3. Select Atlassian Intelligence from the toolbar, and then select Draft Reply.
Alternatively, use /draftreply.
You can copy, insert, or edit the reply as needed.
MAINTAIN APPROVAL HISTORY WHEN BYPASSING APPROVALS
ROLLING OUT
This change allows users to bypass approvals while preserving approval data,
preventing data loss and improving history tracking.
During an approval state of a workflow, an issue can't transition to the
approved or declined status until all approval decisions are finalized.
However, transitions other than ‘Approve’ or ‘Decline’ can be used to manually
transition issues and bypass the approval state. Previously, if you transitioned
an issue’s approval state to a status other than ‘Approve’ or ‘Decline’, it
deleted the approval along with any recorded approver decisions from the
database.
As part of this change:
* if an issue’s approval state is transitioned to a status other than ‘Approve’
or ‘Decline’, it will be recorded as a ‘canceled approval’
* we preserve any active approvals (including approver decisions) that exist
for an approval state when an approval state has been bypassed
* all approvals data will be retained in the approvals activity history
* JQL queries will return issues with approvals activity, even if the approval
is canceled.
Tip: To ensure your approval state status and approver decisions are clearly
conveyed to your customers in the portal activity log, check how your workflow
statuses will appear to customers in the portal based on the display names
assigned to each workflow status.
1. From your project settings, go to Request types.
2. Select the name of the request type you want to modify, then select the
Workflow statuses tab.
3. Review and update the Status name to show customer for each workflow status.
ADD PERMISSIONS TO DETAIL FIELDS FOR CUSTOMERS AND ENTITLEMENTS
ROLLING OUT
Jira admins can now configure view and edit permissions for customer and
organization detail fields in projects with the Customer and organization
profiles feature enabled. Permissions can also be set for entitlement detail
fields in projects with the Products and entitlements feature enabled.
To manage permissions for a detail field:
1. Select Actions (•••) next to the detail field.
2. Select Manage permissions in the dropdown menu.
3. Choose your permissions.
4. Select Save.
RESTRICT REQUEST TYPES TO CUSTOMER ACCOUNTS AND ORGANIZATIONS IN JIRA SERVICE
MANAGEMENT
ROLLING OUT
Control who can raise certain requests in both company and team-managed service
projects by giving access not only to users and groups, but now to customer
accounts and organizations - one of your top requested features!
There may be times when only specific customers should be able to raise certain
requests. These could be requests reserved for different departments in your
company, or even those managing multiple clients in external companies. Now you
have the power to restrict specific request types to these customers who don’t
have Atlassian accounts, and with customer organizations, you can save time by
not having to add the same customers to multiple service projects.
Read more about restricting request types
LINK SERVICE PROJECTS TO A HELP CENTER
ROLLING OUT
Jira Service Management Premium and Enterprise users can now link specific
service projects to a help center, ensuring that customers see only relevant
resources.
Linking projects to a help center allows admins to display relevant help
resources on the home page, in topics, and in search results.
To link a service project to a help center:
1. Navigate to Settings > Products > Jira Service Management > Configuration.
2. In the Help center section, select View all help centers.
3. Use the More (…) menu next to the desired help center to access Settings and
manage project links.
This feature is designed to help admins manage multiple help centers
effectively, targeting distinct audience groups with tailored content. Read more
about linking service projects to a help center.
USE THE VIRTUAL SERVICE AGENT IN EMAIL (BETA)
ROLLING OUT
You can now activate the virtual service agent in email (beta) so that your
customers can find the help they need. When your customers send requests to the
email address connected to your project, the virtual service agent responds
using Atlassian Intelligence answers.
Find out more about using virtual service agent in email
VIEW ASSETS OBJECTS ACROSS CHANGE MANAGEMENT FEATURES
ROLLING OUT
Jira Service Management now provides enhanced visibility for Assets objects
within change management features, expanding beyond service-focused insights. By
setting up an Assets objects custom field and adding it to your change and
incident request types, you can:
* View change conflicts on Assets objects, just as you would for affected
services, within specified time ranges from the risk insights panel
* View recent incidents on Assets objects from the risk insights panel
* Monitor Assets in the change calendar by selecting Assets objects from within
your changes.
Read more about connecting Assets schemas with changes
Read more about connecting Assets schemas with incidents
UPDATES TO CREATING LINKED ISSUES IN JIRA SERVICE MANAGEMENT
COMING SOON
When you create linked issues in Jira Service Management projects, you can no
longer upload attachments.
Instead, upload attachments after you create the linked issue.
These changes apply for both commercial and FedRAMP Jira Service Management
projects.
A NEW WAY TO MANAGE ISSUE SECURITY ON REQUEST TYPES IN JIRA SERVICE MANAGEMENT
ROLLING OUT
No longer do you need to add the Security level field to request types, now
manage restrictions all in one centralized place in company-managed service
projects.
Select Restrictions when you are configuring a request type, and from there
you’ll be able to control both who has access to raise requests and view issues.
This gives you more control and confidence when it comes to knowing how request
types are locked down.
Plus for those who use default security levels, you’ll now have better
visibility of how it applies to request types in your project.
NEW ISSUE SECURITY SCHEME FOR COMPANY-MANAGED SERVICE PROJECTS
ROLLING OUT
We’re introducing a new default issue security scheme, a useful starting point
for fast-tracking the implementation of issue security in your new Jira Service
Management company-managed projects.
Previously, restricting access to sensitive or confidential data in issues
required an admin to create an issue security scheme and associated levels,
assign users, groups and/or custom fields, and then add the security level
system field to the relevant request types.
The new issue security scheme will be associated with every new company-managed
service project created using a project template, removing the need to create a
scheme from scratch and enabling admins to quickly and easily implement issue
security levels. It can be used as is or customized to suit the needs of any
teams (like HR, legal, and finance) that need assurance that only certain people
can see particular issues.
Find out how managing issue security is about to get a whole lot easier.
To see this change, you must:
* be on a Standard or Premium plan for Jira Service Management
* be a Jira admin (only Jira admins can configure issue-level security)
* create a new company-managed service project using a project template (after
this feature is released).
To view and configure the issue security scheme:
* Select Settings ( ), then select Issues.
* In the Issue attributes section in the left navigation, select Issue security
schemes.
* You’ll see the ‘Default Issue Security Scheme for JSM' among the list of
available schemes.
The issue security scheme comes with two preconfigured issue security levels:
* Sensitive cases: These work items are only visible to the assignee and the
reporter to lock down access to the most restrictive audience. This is
recommended for use cases like HR case management where the information is
extremely sensitive.
* Service desk team: This will restrict the work item to the reporter and the
service desk team (as well as the assignee, project lead, and project
admins). This is recommended for less critical use cases, such as HR queries,
leave requests, contract management etc.
You can tailor these levels to meet your needs or add your own levels, then
choose one to set as the default security level that will be applied to issues.
Read more about how to manage security levels for issues.
To associate the issue security scheme to an existing company-managed service
project:
* From your project, select More actions next to the project name, then select
Project settings.
* Select Access, then Issue security.
* Select Actions, then Select a scheme or Use a different scheme (to change
schemes).
* In the Scheme drop-down list, select ‘Default Issue Security Scheme for JSM’,
then select Next.
* Select Associate, then select Acknowledge.
Once the scheme has been assigned to your project and you’ve set your default
security level, you can ensure that issues have security fields added by
default.
JIRA PRODUCT DISCOVERY
ENABLE FREE ACCESS LEVEL IN JIRA PRODUCT DISCOVERY
ROLLING OUT NEW THIS WEEK
If your site is on the Free plan, as of November 15th, 2024, everyone with
creator product access will be a project admin. The access permission scheme
cannot be changed.
USE THE GITHUB FOR JIRA APP TO CONNECT GITHUB ENTERPRISE, INSTEAD OF DVCS
Jira admins making a new GitHub connection for a new organisation now need to
install the GitHub for Jira app. The app functions just like the DVCS Connector,
but with better security features and improved performance.
This only applies to new GitHub connections in new organisations. Existing
connections using DVCS are not affected.
Learn more about the GitHub for Jira app.
MAKE A VIEW ACCESSIBLE TO PEOPLE OUTSIDE YOUR ORGANIZATION
ROLLING OUT
This feature enables creators with an Atlassian account and the permission to
make a published view visible to anyone on the Internet who has a link and not
an Atlassian account. That means you can share the link to a published view in
your social media feed, email, or anywhere else you may want to share it, and
anyone can view it.
Find out more about publishing views
UI VISUAL REFRESH AND ENHANCEMENTS
We're changing a few things in the UI to improve your experience.
JIRA PRODUCT DISCOVERY ROADMAPS IMPROVEMENT (PREMIUM EDITION)
ROLLING OUT
When visiting the Roadmap homepage, you can now visualize which projects are
used in each Roadmap.
SEE THE PROJECTS IN YOUR ROADMAP AND FILTER THEM BY PROJECTS
You can now see which projects are contained in each roadmap, and filter your
roadmaps by projects.
In your project, click Roadmaps on the top nav bar to land on your roadmap.
QUICKLY CLEAR YOUR SEARCH QUERY
ROLLING OUT
You can now clear your search query by clicking the X in the search bar.
1. Go to + Project settings > Access.
2. Type something in the search field.
3. Select the X to delete the query.
WE'VE RENAMED THE PROJECT ACCESS RESTRICTIONS
ROLLING OUT
We've changed the way we refer to project restrictions.
NOTIFY IF A GLOBAL FORMULA FIELD HAS MISSING INPUTS.
ROLLING OUT
If a global formula field uses other global fields as input or if one or more of
these fields get removed from the project, a tooltip notifies that the global
formula field has missing inputs.
NEW INFORMATIVE BANNER IN PLANS
ROLLING OUT
The banner that shows up when you are in a plan using an idea field.
CONFLUENCE
SIGNING UP FOR CONFLUENCE FROM JIRA JUST GOT EASIER
ROLLING OUT NEW THIS WEEK
If you’re using Jira and don’t have Confluence you might see a prompt to try it
out. If you select this prompt you will go through a signup flow. Previously,
this flow was full-screen and used an older style of Atlassian branding.
The flow has been updated with new branding. It also opens on a smaller popup
screen that overlays your Jira screen.
The popup will vary depending on which Confluence plan you’re signing up for.
EDITOR: AI COMMAND PALETTE IMPROVEMENTS
ROLLING OUT NEW THIS WEEK
We're making several design updates to improve the Atlassian Intelligence
command palette. The updates aim to help simplify the AI command palette, and do
not impact the use of agents, features, or prompts.
What's new:
* Double backspace to remove tags: You can now select the tag via the backspace
key to either delete the tag or continue typing.
* Tell AI what to do next: The auto-focused field lets you prompt Atlassian
Intelligence with your next command for a fast-follow response.
* Updated footer: The AI command palette footer has been updated from BETA to
general, and is more minimalist in design.
* Simplified free prompts: The Tell Agent suggestion has been removed when
using free prompts to reduce visual clutter.
BE MORE EXPRESSIVE WITH PANELS
NEW THIS WEEK
In addition to the five preset panel options, you can customize panels by
choosing one of the 20 background colors available.
Panels can have emojis, or you can remove the emoji to meet the needs of your
content. The emojis available to you are the same set that you already use in
Confluence; this includes custom emojis you and your teammates added.
1. Add a panel to a page by typing /custom panel or by selecting Custom panel
from the insert menu.
2. Use the floating toolbar to choose a background color and pick an emoji if
you want one.
CONTROL WHAT YOU SEE IN YOUR PRODUCTS
ROLLING OUT
Product recommendations now have controls, so now you can dismiss them or learn
more about why you’re seeing them. These controls are being added to the
recommendations in the app switcher menu which means you'll have more control
and receive better product recommendations.
You can select the three dots next to the recommendation to learn why we have
recommended it or to dismiss it entirely.
The recommendation controls will first be released to both Free and Standard
teams of up to 50 users. Note: Only admins will be able to add a new product by
clicking on the recommendation.
PREMIUM AND ENTERPRISE: CUSTOMIZE A DYNAMIC INFO HUB FOR YOUR ENTIRE COMPANY
WITH COMPANY HUB
ROLLING OUT
Company Hub allows you to customize a beautiful and dynamic company-wide
information central within Confluence, where employees can go for up-to-date
announcements, news, key resources, and more.
Product admins can add a custom name and color scheme along with images, visual
cards, links, and more to instantly craft a hub that looks and feels like your
company's go-to destination.
This feature is rolling out gradually to our Premium and Enterprise customers.
RESTORE AND REATTACH INLINE COMMENTS, EVEN AFTER DELETING HIGHLIGHTED TEXT
ROLLING OUT
Inline comments anchored to highlighted text can get resolved when that text is
changed or deleted during an editing session. It is now possible to restore
those comments by reattaching them to selected text in the editor.
Resolved comments can be accessed from the More actions menu on the toolbar.
Find the resolved inline comment you want to restore, and select Restore
comment.
In the editor, highlight text you'd like to add the comment to, and select Add
comment.
SEAMLESSLY MIGRATE FROM NOTION TO CONFLUENCE WITH BULK IMPORTING
ROLLING OUT
Our new bulk importer tool makes it easy for you to migrate your content from
Notion to Confluence, ensuring a smooth transition and minimal disruption. With
support for importing up to 40,000 pages, including attachments and page
comments, site and organization admins can now move their workspaces with
confidence. The tool also allows you to preserve user data and permission
settings to boost familiar patterns within Confluence.
* Site and organization admins can import to 40,000 pages from Notion to
Confluence, including attachments, page comments, @mentions, and author
information.
* Preserve user data and permission settings for a more seamless transition.
* Supports importing entire workspaces or selected pages.
* A completion report email shows an overview of the import outcome, providing
transparency and simplifying following up.
Select Import from other tools in the Spaces menu and follow the step-by-step
guide to import your content from Notion.
CATCH UP QUICKLY WITH PAGE COMMENTS SUMMARY
ROLLING OUT
Now, Atlassian Intelligence can summarize page comments for you, making it
easier and faster to catch up on important feedback. Just navigate to the bottom
of the page, above the first page comment, and select Summarize comments.
New comments since you last checked? Select the refresh icon to generate a
summary that includes all the latest feedback.
ADMINS CAN NOW CREATE AUTOMATION RULES FOR PUBLIC LINKS
ROLLING OUT
We're adding the ability to create automation rules directly from the public
links setting on a page.
When an admin on a Confluence space with automation turns a page's public link
on or off, they will see a prompt to create a new automation rule to manage
public links.
CREATE CONFLUENCE WHITEBOARDS DIRECTLY FROM YOUR JIRA BACKLOG
ROLLING OUT
With Confluence whiteboards, you can plan freely and execute quickly. Create a
whiteboard directly from your Jira backlog, copy backlog issues to the
whiteboard, and plan however you want.
Here are some suggestions for things you can do with Confluence whiteboards:
* Use award-winning templates such as a prioritizing and planning matrix
* Import Jira issues directly into your new planning whiteboard
* Link sticky notes and issues to show dependencies and timelines
* Turn sticky notes into Jira issues
* Engage teammates with real-time, group editing
* Collaborate using stamps, timers, and more
If an admin has three or more issues in their backlog, they'll see the button
that allows them to add Confluence and start using a whiteboard. Once a team has
Confluence, anyone with access to Confluence — including admins and end users —
will see the button on their backlog that allows them to create a whiteboard.
You can remove this button anytime by turning off all product recommendations at
in your Jira settings. Note: if you add Confluence and then turn off product
recommendations, you will lose this button.
FREE USER LIMIT AWARENESS
ROLLING OUT
We're making it easier to know when your team is near or has reached the Free
user limit.
A modal will appear when your team is near and reaches the Free plan user limit
of 10 users. Plus, the button at the top right of your screen with change colors
to let you know you're nearing the limit.
EFFORTLESS CONTENT ARRANGEMENT WITH DRAG-AND-DROP
ROLLING OUT
This update introduces new drag-and-drop functionality for top-level elements in
the Confluence editor, making it easier than ever to arrange your content. This
feature enhances the user experience by allowing smooth content movement,
reducing the need for cut-and-paste actions, and providing a more intuitive and
modern editing experience.
What's new:
* Drag and drop for top-level elements: A new drag handle makes it easy to
rearrange any top-level element on your page.
* Instant selection: Select any element with a single action on the drag handle
for fast and convenient movement.
* Auto-scroll functionality: Move content above or below the fold with
automatic scrolling, ensuring smooth navigation while rearranging elements.
FIXED COLUMN WIDTHS FOR TABLES
ROLLING OUT
We’re pleased to introduce a new feature that enhances your control over your
tables. You can now set column widths to fixed, ensuring that your table layout
remains consistent even on narrow screens. This option is available in Table
options in the table toolbar and is unchecked by default, allowing tables to
scale as they always have. For those who prefer their tables to respond
dynamically to screen sizes, we’ve increased the maximum scaling to give your
tables even more flexibility.
How to use:
1. Insert or select a table on your page.
2. Select the Table options icon in the table toolbar.
3. Select the Fixed column widths option to prevent your table columns from
scaling down on narrow screens.
This update allows you to maintain the integrity of your table layouts across
different screen sizes, providing a more consistent viewing experience.
CREATE A NEW PAGE DRAFT WHILE EDITING A PAGE WITH GREATER SPEED AND SIMPLICITY
ROLLING OUT
While editing a page, you can now type /Create Confluence page and instantly
create a brand new page with greater simplicity and speed than ever before. Now,
this action will automatically generate a new page draft in a new tab and insert
a link to that draft within the page you're currently on.
RENAME SPACE KEY IN CONFLUENCE CLOUD
ROLLING OUT
We’re adding the ability to change your space key. Renaming space keys can help
with accurately representing a company to users and publicly as organization
changes take place. It can also help to prevent conflicts during migrations for
newly created spaces.
* Space admins can rename their space (for example, during acquisitions,
organization restructuring, or if the department, username, or team name
changes).
* The old space key will redirect to the new URL.
To rename your space key:
1. As a space admin, go to Space settings > Manage space > Space details.
2. Select Edit space details.
3. Enter your new name in the Space key text box.
4. Select Save.
ENHANCED INLINE COMMENTING
ROLLING OUT
You can now comment directly on inline elements such as emojis, statuses,
mentions, dates, and inline cards (Smart links). Users can now leave comments on
these specific elements, streamlining the commenting process and making it more
intuitive and efficient for providing feedback and collaborating on documents.
IMPORT MIRO BOARDS TO CONFLUENCE WHITEBOARDS
ROLLING OUT
Keep all your work in one place by importing your boards from Miro to editable,
native elements in Confluence whiteboards.
Export your Miro boards as vector PDFs and import to Confluence whiteboards for
this functionality. Read more about how to do this and what we support.
ADD HYPERLINKS TO WHITEBOARDS
ROLLING OUT
Hyperlinks can now be added to whiteboards text.
Easily share links with your collaborators on a whiteboard through free text or
text within an element. Hyperlinked text will appear blue.
UPDATES TO CONFLUENCE'S DAILY DIGEST
ROLLING OUT
We're excited to roll out new enhancements for our daily digest. In this update,
you'll receive a summary of the pages and blogs you've watched and viewed.
MORE CONTROL OVER NOTIFICATIONS
ROLLING OUT
Page owners no longer receive notifications by default when someone interacts
with their page. Instead, they can opt-in to notifications by choosing to Watch
the page. This change reduces the noise of unnecessary communications (for
example, when pages are no longer actively monitored or updated) — and improves
the value of the notifications that do appear in the person's inbox and message
feeds.
Read more about how to watch a page
BULK DUPLICATE AND DELETE COMPONENTS IN THE AUTOMATION RULEBUILDER
ROLLING OUT
We're introducing a new feature that allows you to select multiple components at
once in the automation rulebuilder and either duplicate or delete them. This
change affects both Jira and Confluence, and should help to improve efficiency
in the rulebuilder, as you'll no longer need to select each component one at a
time to edit them.
To select and edit multiple components at once:
1. Hold down the Ctrl / Command key and click the left button on your mouse or
touchpad.
2. Select the number of components you want to duplicate or delete.
3. Once the components are selected, you can use the new menu to duplicate or
delete them.
COLLABORATE MORE EASILY ON WHITEBOARDS BY FOLLOWING YOUR TEAMMATES
ROLLING OUT
Follow your teammates wherever they are on Confluence whiteboards for easier
collaboration.
You can follow anyone by clicking their avatar at the top of the whiteboard.
SAVE AUTOMATION RULES IN A DISABLED STATE
ROLLING OUT
We're introducing a new feature that allows you to save automation rules in a
disabled state, which means they are draft rules that you can come back to edit
and turn on later. Previously, rules couldn't be saved as drafts and had to be
turned on immediately after creation. This new feature provides more freedom for
users and allows you to more effectively edit and refine your rules before
turning them on.
To get started with this change:
1. Open either Jira or Confluence automation.
2. Select Create rule and create your desired rule in the rulebuilder.
3. Click on the dropdown arrow next to the Turn on rule button.
4. Select Save rule without enabling.
5. You'll now be able to see the draft rule under your Rules list in
automation. It will appear as 'Disabled'.
6. When you're ready to turn on the rule, move the Enabled toggle to the right
so a tick appears.
7. Your rule is now turned on and ready to use.
NEW ANALYTICS FOR COMPANY HUB
ROLLING OUT
We’re excited to roll out analytics for your Company Hub. Understand how your
hub is performing and discover what content is most relevant to your users. See
the total number of visits, unique visitors, clicks, and more! You can also
filter your dates by a specific time frame to see which content has the most
views, click-through rates, and unique visitors.
To access this feature,
1. Navigate to your Company Hub editor.
2. Select the more … icon on the top right corner of your page.
3. Under Company Hub settings, select Analytics.
4. Filter the data based on a specific date range to see specific analytics or
content.
IMPROVED JIRA ISSUE CREATION FROM A PAGE, FEATURING ATLASSIAN INTELLIGENCE
ROLLING OUT
We’ve improved the Create Jira issue menu option in Confluence pages.
When you select text, you can now create a single issue in the right-side panel.
This gives you access to all Jira issue fields while staying in context of the
page you’re viewing.
We’ve also added the ability to select text and ask Atlassian Intelligence (AI)
to generate your issue for you. AI will use both the selected text and the
surrounding content to generate a Jira issue’s summary, description, assignee,
and other relevant fields.
Atlassian Intelligence is available and automatically activated for all products
on Premium and Enterprise plans. Organization admins can manage Atlassian
Intelligence preferences from Settings > Atlassian Intelligence in Atlassian
Administration.
SLACK NOTIFICATIONS FOR INVITED USERS
ROLLING OUT
We're introducing a new Slack notification to remind invited users to join an
instance if they haven't accepted their invitation yet.
This notification will be sent automatically. No action is required for setup.
AUTOMATE YOUR RESPONSE WHEN SENSITIVE DATA IS DETECTED
ROLLING OUT
Guard Detect sends an alert when someone updates a Confluence page containing
certain types of sensitive data, such as credentials, financial, or identity
data.
You can now harness the power of Confluence automations to streamline your
workflow when sensitive data is detected. Build your own rule using the new
content scanning alert trigger, or try one of the templates to get you started.
Not sure how automations would help your workflow? Here’s some ideas:
* Classify the page that contains sensitive data.
* Restrict the page and add a comment or send an email to the actor to explain
your company's policy on sensitive data.
* Create a Jira ticket to track the next steps for cleaning up the data.
You can configure the trigger to perform an action when any content scanning
alert is generated, or just for specific alerts, such as API keys or credit card
numbers. Thanks to the huge number of actions and conditions available in
Confluence automation, the possibilities are endless.
How does automation work with Guard Detect?
The fastest way to get started is to use a template:
1. In Confluence, go to Automations.
2. Select the Templates tab.
3. Select the Respond to security alerts category
4. Select a template and follow the prompts to configure it.
You’ll also see an option to add an automation rule in your next content
scanning alert.
We suggest you create a rule in a test space first. Once you’re happy with the
rule, you can create a global rule. If you have multiple Confluence instances,
you’ll need to configure the rule in each instance.
Content scanning alerts are available with Atlassian Guard Premium. Automation
is available with a Confluence Premium or Enterprise plan.
MANAGE YOUR CONFLUENCE SPACES
ROLLING OUT
Introducing a new feature for product admins to view and manage all their
Confluence spaces with supportive metadata and actionable insights. This feature
is available to customers on all Confluence plans.
Admins can now easily view, filter, and take actions on their spaces, such as
archiving or deleting inactive spaces, copying permissions (for customers on
Confluence Premium and Enterprise editions only), and more.
To get started with this change:
Admins can select Spaces in Confluence settings.
CUSTOM FIELDS AVAILABLE IN THE AUTOMATION SMART VALUES PANEL
ROLLING OUT
We're adding a new feature to the smart values panel in Jira and Confluence
automation. The panel will now have an additional filter called Custom fields,
which will contain up to 50 custom issue fields from the current instance you
have access to. You can search and copy these custom fields to use them while
creating rules in the rulebuilder. Custom fields can be filtered by either the
smart value or the untranslated name using text input. We will also display if
these fields can be used globally or are bound to a single project.
To start using this feature:
1. Open the automation rulebuilder.
2. Select a trigger for your rule.
3. Add an action that has smart value text fields, such as the Log action, Send
web request or Create issue action.
4. Select the {} button to open the smart values panel.
5. Select the Custom fields tab to browse available custom issue fields.
6. You can now copy and use these custom fields in your rule.
Learn more about using smart values in Atlassian automation
NEST EXPANDS WITHIN EXPANDS
ROLLING OUT
We've introduced the ability to nest expands within other expands in the editor.
This can help you organise the hierarchy of content, improving readability and
navigation within documents.
* Nested expands: You can now create nested expands within other expands,
allowing for deeper levels of content organization.
* Improved Editor functionality: The editor now supports more complex content
structures, making it easier to manage detailed information.
INSERT AND SHARE ANCHOR LINKS WITH GREATER EASE AND CLARITY
ROLLING OUT
The anchor link macro (formerly called the "anchor macro") has been updated to
look and function more intuitively. Now, it is easier than ever to create a
hyperlink to a specific part of a page. Upon inserting an anchor link, you'll be
able to quickly select Copy link from the floating toolbar and share that link
wherever needed.
QUICK CALCULATIONS IN CONFLUENCE DATABASES
ROLLING OUT
Calculate sums, averages, min, max, and other insights with quick calculations
in Confluence databases.
Right-click on any field, go to Calculate, and select the calculation you want
to see. Results appear at the bottom of the database.
MANAGE AND CUSTOMIZE YOUR COMPANY HUB WITH GREATER EASE
It's easier than ever to control and calibrate who has edit access to your
company hub. You can now access Hub permissions directly from the More actions
(...) menu while editing your hub page, to add or remove hub editors as needed.
We've also improved some Company Hub adjacent settings in Customize navigation
and General configuration. This makes it more intuitive to customize your
Confluence navigation bar to fit your company's branding or preferences.
CUSTOMIZE DURATION FOR WAITING FOR A RESPONSE WHILE RUNNING THE AWS SSM DOCUMENT
AND RESUME RULE IN CASE OF NO RESPONSE
ROLLING OUT
When running the AWS SSM document, you can configure the action to wait for a
response for a duration of 1 to 15 minutes. Additionally, you can now set the
rule to resume even if AWS SSM doesn't return a response within the specified
time.
CUSTOMIZE DURATION FOR WAITING FOR A RESPONSE WHILE RUNNING A QUERY IN NEW RELIC
AND RESUME RULE IN CASE OF NO RESPONSE
ROLLING OUT
When running a query in New Relic, you can configure the action to wait for a
duration of 1 to 15 minutes. Additionally, you can now set the rule to resume
even if New Relic doesn't return a response within the specified time.
CUSTOMIZE DURATION FOR WAITING FOR A RESPONSE WHILE LAUNCHING A JOB TEMPLATE IN
ANSIBLE AND RESUME RULE IN CASE OF NO RESPONSE
ROLLING OUT
When launching a job template in Ansible, you can configure the action to wait
for a duration of 1 to 15 minutes. Additionally, you can now set the rule to
resume even if Ansible doesn't return a response within the specified time.
CUSTOMIZE DURATION FOR WAITING FOR A RESPONSE WHILE STARTING A RUNBOOK IN AZURE
AND RESUME RULE IN CASE OF NO RESPONSE
ROLLING OUT
When starting a runbook in Azure, you can configure the action to wait for a
duration of 1 to 15 minutes. Additionally, you can now set the rule to resume
even if Azure doesn't return a response within the specified time.
CUSTOMIZE DURATION FOR WAITING FOR A RESPONSE IN VIRTUAL MACHINE IN AZURE AND
RESUME RULE IN CASE OF NO RESPONSE
ROLLING OUT
When restarting Virtual Machine in Azure, you can configure the action to wait
for a duration of 1 to 15 minutes. Additionally, you can now set the rule to
resume even if Virtual Machine in Azure doesn't return a response within the
specified time.
WE'VE SIMPLIFIED SPACE CREATION
ROLLING OUT
With just two kinds of pre-set spaces, each made to suit a specific purpose,
creating a space is easier than ever before. Choose between Knowledge base and
Collaboration, add a description to the overview, and dive into content creation
faster than ever before with one of our suggested templates. Or, if you know you
want something really specific, choose Custom to manually configure the features
and settings for your space.
To read about these changes in more detail, check out the Community post.
To create a space:
1. Select Create from the Confluence navigation bar at the top of the screen.
2. Select Space from the dropdown menu.
3. Choose the option that best fits the purpose of the space you're creating.
4. Confirm your choice, making changes to the defaults as needed.
ANALYTICS IS NOW EASIER TO USE
ROLLING OUT
We’ve redesigned Confluence Analytics across Page, Space, and Site Analytics to
improve its look and feel and make it easier to interact with your data.
The following changes apply to Pages, Space, and Site Analytics:
You can now select from a set of preset “time-range” filters such as the last
seven days and year-to-date and you can use a drop-down to select grouping by
weeks or other timeframes.
You can now select Total views and Unique viewers directly from the chart and
make both visible at the same time.
It's now easier to find users, content, or spaces with the new search bar
available in all analytics tables.
For page analytics, we've made these changes:
On the Page Analytics Overview, we've added quick access to the most-used
metrics with summary cards for views, viewers, and mentions.
You can also send reminders to mentioned teammates who haven’t viewed the page
yet—available from both the Views tab and the Mentions tab.
To simplify Page Analytics and reduce clutter, we’ve removed the rarely-used
Attachments tab from the Analytics screen.
NEST MEDIA AND CODEBLOCKS IN QUOTES
ROLLING OUT
We’ve added the capability to nest media (images, videos, etc.) and codeblocks
inside of quotes in the editor. This allows for better context when formatting
quotes.
* Media in quotes: Users can now embed images, videos, and other media types
within quotes, enhancing visual context.
* Codeblocks in quotes: Codeblocks can now be nested inside quotes, making it
easier to reference and highlight code snippets within discussions.
MENTION USERS IN AUTOMATION ACTIONS
ROLLING OUT
You can now mention users in your Automation for Confluence rules. The Add
comment and Publish page actions now support mentioning users by their
"accountId" and by smart values such as page.owner.accountId.
To mention a specific user:
* Visit their profile page and copy the characters at the end of the URL:
* https://hello.atlassian.net/wiki/people/_557057:1d4fd7f4-bbac-4466-82ee-aaabbbccc_
* Add [~accountId:<user's account ID>] to the action component.
To mention a user with a smart value:
* Replace the account ID with any smart value that includes the "accountId"
field.
* For example: [~accountId:page.owner.accountId]
EDITOR: NESTED DRAG AND DROP
ROLLING OUT
We are introducing an enhancement to the drag and drop feature in the Confluence
full-page editor, allowing you to nest content within certain elements. This
update aims to reduce the reliance on cut and paste actions to improve the
efficiency of your content creation.
* Single-click nesting: Drag and drop to nest content such as tables, code
blocks, expands, panels, and layouts.
* Improved content management: The new feature supports nesting of paragraphs
containing inline elements, making content organization more intuitive.
* Enhanced table interactions: Nest within tables, which represents the highest
proportion of nesting scenarios, is now more seamless.
ENHANCED TABLE FEATURES IN THE COMMENTS EDITOR
ROLLING OUT
This update brings a new, improved table experience to the comments editor,
matching the capabilities of the full-page editor. It ensures consistent and
enhanced table functionality across different editor surfaces, reducing
cognitive load and preparing for future platform-wide adoption.
* Custom table widths: Adjust table widths to fit your content needs for
greater flexibility.
* Drag and drop: Easily reposition tables within the comments editor for a more
intuitive editing experience.
* Table alignment: Use new alignment options to better organize and present
your data.
SMART BUTTONS COMING TO TEMPLATES AND BLUEPRINTS
ROLLING OUT
You can now add automation smart buttons to user-created templates and page
blueprints. When someone creates a page with a template that has a smart button,
they will be able to configure the button.
In space settings or admin settings, find Templates and blueprints and edit a
template. Type /smart button to add an automation smart button.
When any user creates a page using your template, they can select the button to
configure each its fields.
ROVO CUSTOMER ADMINS CAN NOW ADD BOOKMARKS
ROLLING OUT
Admins (organization, site or product) on sites with Rovo can now add bookmarks
to highlight particular URLs in Rovo Search, based on specific search terms. You
can bookmark any URL - it doesn’t need to be in your Atlassian products or
previously found in search.
There are two different methods to add bookmarks depending on whether you are a
organization admin, or a site/product admin.
How to add or edit Rovo Search bookmarks
TASK EDITING PERMISSIONS FOR LIVE PAGES
ROLLING OUT
This update introduces a new "request to edit" feature for tasks on Live Pages,
allowing users without edit access to request permission to make changes.
* Request to edit: Users can now request edit access for tasks on Live Pages,
if they currently have view-only access.
* Admin approval: Admins receive notifications for edit requests and can grant
or deny access directly from the notification.
* Access tracking: All edit requests and approvals are logged for better
tracking and auditing.
EDITOR: ADD MEDIA FROM WEB LINKS
ROLLING OUT
You can now add media, including images and videos, directly from web links into
your Confluence pages. This is an update to the existing image upload process.
In the Add image, video, or file toolbar dropdown and backslash command palette,
you can now upload files or media from links.
* Image and video upload from web links: The new feature allows you to insert
media by pasting a URL, making it faster for you to add online resources to
your content.
* Updated toolbar and quick actions: The toolbar and quick action commands now
open a popup with two tabs, "file" and "link", for more flexible media
insertion.
SUMMARIZE WHITEBOARDS WITH ATLASSIAN INTELLIGENCE
ROLLING OUT
Save time and get the details you need to do your work faster by generating a
summary of the content on an whiteboard using Atlassian Intelligence.
1. Go to the Confluence whiteboard you want to summarize.
2. Select Summarize from the top right (to the left of the share button).
3. Atlassian Intelligence will generate a summary of the whiteboard's contents.
At this time, summaries generated by Atlassian Intelligence don’t include
content from images or links.
USE AUTOMATION RULES TO ADD TEXT TO NEW PAGES
ROLLING OUT
The Publish new page automation component now supports adding text to the body
of the page. We're adding an additional field that allows you to input content
that will be added to the page when it's created.
Add the Create page action to your automation rule and input your custom text in
the Page content field.
WHITEBOARDS VOTING IMPROVEMENTS
ROLLING OUT
Run more flexible voting sessions in Confluence whiteboards with anonymous
voting and the ability to mark yourself as done.
You can also delete old voting sessions, and hide votes on the whiteboard as
needed.
SUMMARIZE CHANGES TO A PAGE OR BLOG POST
ROLLING OUT
Now when Premium and Enterprise customers visit a page for the first time in a
while, they can use Atlassian Intelligence to generate a brief summary of
changes since their last visit. Use this feature to quickly catch up on changes
to a project plan after an important review, or to get a sense of what you
missed while you were on vacation.
Atlassian Intelligence will only generate a summary if someone has edited the
page since your last visit. If there aren't any changes to summarize, it will
present you with a summary of the page to help you refresh your memory on the
key points.
Atlassian Intelligence is available to all customers with Premium and Enterprise
plans. Organization admins can manage Atlassian Intelligence preferences from
Settings > Atlassian Intelligence in Atlassian Administration.
To summarize changes using Atlassian Intelligence:
1. Navigate to a Confluence page or blog post that you’ve visited before.
2. Select Summarize changes from the drop-down menu in the Summarize button on
the top right.
3. Atlassian Intelligence will generate a summary of changes since you last
visited the page or post.
You can copy the summary to your clipboard, rate the quality of the summary, and
provide feedback on the feature using the buttons at the bottom of the summary
panel.
ADDING CUSTOM FIELDS AND COMPATIBLE VALUES FILTERS TO CONFLUENCE AUTOMATION
ROLLING OUT
We're adding two new features to the Smart Values Panel in Confluence
automation. The first feature will appear as a tab named Compatible values which
can be used to view the smart values that are most compatible with the
components in your rule.
We're also adding a Custom fields feature to Confluence automation. This feature
will also appear as a tab in the Smart Values Panel, and allow you to see which
issue field smart values can be used for any related Jira components in your
rule. If your rule contains multiple connections to Jira, all available custom
issue fields from these connections will be combined under a single Custom
fields tab.
We’ve also made Jira-specific smart values available in Confluence automation,
so if you have used a Jira component in your rule, the relevant Jira smart
values will be avaliable in the Smart Value Panel.
To get started with this change:
1. Navigate to the automation rulebuilder in Confluence.
2. Create your desired rule.
3. Select any component in your rule that requires you to enter a message, such
as the Send email component.
4. Select the { } button to open the Smart Values Panel.
5. Select either the Compatible values or Custom fields tab to view relevant
smart values.
6. Copy your desired smart value and paste it into your message.
7. Once you're finished creating and editing your rule, turn it on.
8. Your rule is now ready to go!
CLASSIFY CONTENT FROM THE MORE ACTIONS MENU
ROLLING OUT
You can now classify content by selecting More actions (•••) > Classify content.
Data classification is available in Confluence, Jira, and Jira Service
Management and requires an Atlassian Guard Premium subscription.
You can classify content once your organization admin has set up classification
levels for your organization.
To classify an item:
1. Edit the item (only required for pages and blogposts).
2. Select More actions (•••) > Classify content.
3. Choose a classification level.
4. Select Update.
More about data classification:
* Classify a page or blogpost
* Classify an issue
* Classify a request
* Set a default classification level for content
* Set a default classification level for issues
* Set a default classification level for requests
PREVENT PEOPLE FROM USING PUBLIC LINKS IN SPECIFIC SPACES
ROLLING OUT
Data security policies allow you to use rules to control how users, apps, and
people outside the organization can interact with content such as Confluence
pages and Jira issues.
You can now use the public links rule to prevent people creating and accessing
public links in particularly sensitive Confluence spaces. Previously, this was
only available for policies that covered classification levels or entire
Confluence instances. How the public links rule works
The public links rule requires Atlassian Guard Standard (formerly known as
Atlassian Access).
To create a new data security policy or view existing policies:
1. Go to admin.atlassian.com. Select your organization if you have more than
one.
2. Select Security > Data security policies.
DATABASES-FRONTEND-DOUBLE-CLICK-EXPERIMENT
ROLLING OUT
Now double-click on a cell to enter edit mode in Confluence databases for a more
controlled editing experience.
Values copied to your clipboard can be pasted directly into the database by
selecting a cell and pasting.
VOTING IN CONFLUENCE WHITEBOARDS
ROLLING OUT
Simplify collaborative decision-making with voting in whiteboards. Use it for
brainstorming, retrospectives, and more with your team. Anyone on the whiteboard
can start, manage, and conclude voting sessions.
View detailed results with the top-voted items and individual votes.
ADD NUMBERED ENTRIES TO CONFLUENCE DATABASES
ROLLING OUT
Add numbered entries to your databases in Confluence for better organization.
Enable Number entries from the Table Layout settings for a view.
EDITOR: MEDIA INTERACTION IMPROVEMENTS
ROLLING OUT
We are improving media interactions within editor for a more intuitive workflow
and experience.
* Double click to open media viewer: You can now double-click to open the media
viewer in both Live Pages (view and edit modes) and the default editor,
providing a quicker way to access media content.
* Navigate media within documents: You can now navigate all media within a
document, making it easier to manage and review multiple media files when in
the media viewer.
EDITOR: SPOTLIGHT FOR INLINE COMMENTS
ROLLING OUT
We are introducing a spotlight guide to inline comments, if you have not used a
comment on inline elements before.
Spotlight on inline elements: When you select content that includes an inline
element, a spotlight will appear to provide guidance on where you can now leave
comments.
CREATE GOOGLE DOCS IN YOUR GOOGLE DRIVE WITH JIRA AND CONFLUENCE AUTOMATION
ROLLING OUT
We’re introducing a new component to Jira and Confluence automation that allows
you to create a Google Doc in your Google Drive by simply executing a rule. This
feature will help you to create Google Docs more quickly and easily, as you’ll
no longer need to create them manually - Atlassian automation can do it for you!
To get started with this change:
1. Navigate to the automation rule builder in Jira or Confluence.
2. Select a trigger for your rule.
3. Select the Create Doc in Google Drive action and add it to your rule.
4. Select a Google Drive folder for your Google Doc to be placed in. Your Doc
will be placed in your My Drive folder if you don't have permission to
select a location for it.
5. Add a title and any body content you want your Google Doc to contain.
6. Add any other desired components to your rule.
7. Once you've edited and finalized your rule, turn it on.
8. Your rule is now ready to go.
CLEAR DATE AND TIME FILTERS IN THE AUTOMATION AUDIT LOG
ROLLING OUT
We're introducing a new feature to Jira and Confluence automation that allows
you to clear all selected filters in the audit log with a click of a button.
This change will help you to save time and improve efficiency, as you'll no
longer need to manually de-select all the selected filters yourself.
To start using this feature:
* Open the audit log in either Jira or Confluence automation.
* Apply any desired date and time filters to the audit log.
* Once you are done with these filters, select the Date and time button.
* Select Clear filter. All selected date and time filters will automatically be
de-selected.
* Your audit log will now have no date and time filters applied to it.
Learn more about using the audit log in Jira and Confluence automation
BITBUCKET
PROJECT AND WORKSPACE CUSTOM MERGE CHECKS
NEW THIS WEEK
Bitbucket Cloud now allows custom merge checks to be configured at the workspace
and project levels and enables rules set at higher levels to be inherited,
reducing redundant configurations. The UI has also been redesigned to offer
clearer guidance around the initial setup of the feature and make it easier for
admins to configure checks across all levels.
As a workspace admin, go to workspace settings > custom merge checks
COMPASS
UPGRADE YOUR COMPASS GITHUB APP TO ALLOW COMPASS TO INGEST PULL REQUEST DATA
ROLLING OUT
Accept the updated permissions for your Compass GitHub app to authorize Compass
to enrich the PR data/insights we show you in Compass.
Upgrade your Compass GitHub app:
1. In GitHub, go to the organization settings for the organization that you've
connected the Compass app to.
2. Select GitHub apps on the left sidebar.
3. Select the Review request link.
4. Enter your GitHub password.
5. Select Accept new permissions.
You're now on the latest version of the Compass GitHub app.
CUSTOM COMPASS COMPONENT TYPES SUPPORT IN JIRA
ROLLING OUT
We're introducing a new capability in Compass that allows product admins to
create component types based on the terminology their teams use to categorize
them. Custom type names will be supported in Jira, but will use the OTHER icon.
In Compass, product admins can create up to 14 component types, but anyone on
their Compass plan can use them. This customization helps software teams better
group components at a high level across their distributed architecture.
ATLASSIAN ANALYTICS
VISUAL SQL: WRITE CUSTOM FORMULAS USING ATLASSIAN INTELLIGENCE (AI)
ROLLING OUT
You no longer need to worry about memorizing SQLite syntax for custom formulas.
You can use natural language to tell AI how you want to transform the data in
one of your columns, and AI will generate the SQLite expression for you.
To try it out:
1. Add a Formula column or Apply formula step.
2. Select Custom from the formula options.
3. Select AI.
4. Use natural language to describe how you want to transform your data.
5. Select Submit.
Powered by Confluence and Scroll Viewport.
Atlassian
* Your Privacy Choices
* Privacy Policy
* Terms of Use
* Security
* © 2024 Atlassian
This site uses cookies to improve your browsing experience, perform analytics
and research, and conduct advertising. To change your preferences, click Manage
preferences. Otherwise, clicking Accept all cookies indicates you agree to our
use of cookies on your device. Clicking Reject all cookies means you do not
agree to our use of non-strictly necessary cookies on your device.Atlassian
Cookies and Tracking Notice
Manage preferences Reject all cookies Accept all cookies
MANAGE PREFERENCES
When you visit any website, it may store or retrieve information on your
browser, mostly in the form of cookies. This information might be about you,
your preferences or your device and is mostly used to make the site work as you
expect it to. The information does not usually directly identify you, but it can
give you a more personalized web experience. Because we respect your right to
privacy, you can choose not to allow some types of cookies. Click on the
different category headings to find out more and change our default settings.
However, blocking some types of cookies may impact your experience of the site
and the services we are able to offer.
More information
Accept all
STRICTLY NECESSARY COOKIES
Always Active
These cookies are necessary for the website to function and cannot be switched
off in our systems. They are usually only set in response to actions made by you
which amount to a request for services, such as setting your privacy
preferences, logging in or filling in forms. You can set your browser to block
or alert you about these cookies, but some parts of the site will not then work.
These cookies do not store any personally identifiable information.
TARGETING COOKIES
Targeting Cookies
These cookies may be set through our site by our advertising partners. They may
be used by those companies to build a profile of your interests and show you
relevant adverts on other sites. They are based on uniquely identifying your
browser and internet device. If you do not allow these cookies, you will
experience less targeted advertising.
FUNCTIONAL COOKIES
Functional Cookies
These cookies enable the website to provide enhanced functionality and
personalisation. They may be set by us or by third party providers whose
services we have added to our pages. If you do not allow these cookies then some
or all of these services may not function properly.
PERFORMANCE COOKIES
Performance Cookies
These cookies allow us to count visits and traffic sources so we can measure and
improve the performance of our site. They help us to know which pages are the
most and least popular and see how visitors move around the site. If you do not
allow these cookies we will not know when you have visited our site, and will
not be able to monitor its performance.
Back Button
COOKIE LIST
Search Icon
Filter Icon
Clear
checkbox label label
Apply Cancel
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label
Reject all Confirm my choices