Jump to content

Atlassian Product Updates

These are the official product updates from Atlassian for their Cloud and Data Center products. We list them here so we can create content related to these release notes.
Show all categories

⚠️Introducing 'work' as the new collective term for items tracked in Jira Cloud

As more teams make Jira their home for work, we’re committed to improving the language in our tools to better reflect the diverse ways you define and manage your work.
We’re introducing work as the new collective term for all items tracked in Jira. We’re also exploring ways to incorporate the language you use for your own work types.
Read more about these changes on the Atlassian Community.
Key changes
We're replacing ‘issue’ terminology with work as the collective term for all items tracked across Jira Cloud, including Jira Service Management, and Jira Product Discovery.
Your team’s work type terminology will be reflected in Jira whenever you create new work or reference specific items.
When it's not possible to use your specific language or when we’re referring to various types of work collectively, we'll use the term work item.

Benefits
Reduced technical jargon: Clear and simplified language that aligns with the needs of all teams, making it easier to collaborate on work and onboard new team members.
Jira speaks the language of your team: By embracing the work types you use, we aim to make Jira intuitive for everyone, whether you're a tech-savvy developer or a creative campaign manager
Reason for the change
Jira was originally developed as a bug tracker, designed to manage ‘issues' – and for years, that’s how we’ve referred to the work teams track in our tools. But, as our products have evolved, so have the use cases they support.
Today, Jira serves a diverse array of teams, each with unique workflows. We believe that the true power of Jira lies in its flexibility to represent all kinds of work. We’ve heard from you that the term ‘issue’ can be limiting and somewhat confusing in the context of your work.
How to prepare for the change
Apart from informing your teams, there's nothing you need to do in product to prepare for this update.
Jimi Wikman
💫 Jimi Wikman

Quickly set up your service project with the new Get started page

We’re introducing the new Get started page which outlines key onboarding tasks and their default settings. You can get your project up and running quickly, just by reviewing the default settings.
The Get started page will appear automatically in the left navigation, once you create a new project. It will be available for all new company-managed projects except the ones created with the ITSM or Blank templates.
Key changes
 
 
Benefits
On the Get started page, you can :
review default configurations in one place
try resolving a sample request
learn from help articles and videos
join the Atlassian Community
Jimi Wikman
💫 Jimi Wikman

🚨 SCIM API keys expire in one year

We're changing the expiration date for SCIM API keys from an infinite lifespan to a one year expiration date: This change applies only when you:

-set up user provisioning for the first time
-regenerate an existing SCIM API key
This change does not affect existing SCIM API keys for now.
We’re making this change to reduce security risk for any leaked or stolen keys and to encourage you to rotate your keys. If a key is leaked or stolen, its limited lifespan prevents attackers from using it indefinitely to access sensitive information.
When is this changing?
-On December 15, 2024, SCIM API keys expire in one year. This includes a SCIM API key that we create when you set up user provisioning or when you regenerate a SCIM API key.
 
How to view the SCIM API key’s expiration date when you set up user provisioning:
Log in to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Identity providers.
Select your Identity provider Directory.
Select Set up user provisioning and follow the prompts.
View API key expires date in User provisioning.
How to view the SCIM API key’s expiration date when you regenerate an API key:
Log in to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Identity providers.
Select your Identity provider Directory.
Select Regenerate API key from […} and follow the prompts.
View API key expires date in User provisioning.

Jimi Wikman
💫 Jimi Wikman

Highlight work with color in your list

Identify and highlight key work that needs your attention with format rules in your list. With a format rule, you can automatically format individual cells or entire rows with colors, when specific criteria is met.
For example, to highlight work that’s running behind schedule, you could create the rule: red row when due date is before today. More examples of format rules and their purpose, plus how to create a format rule.
To create a new format rule in your list:
Go to your project, and select List.
Select Format.
Select + Add a rule in the Format rules sidepanel.
Jimi Wikman
💫 Jimi Wikman

Use third party secret providers in Bitbucket Pipelines

Bitbucket Pipelines is excited to introduce third party secret integration. This powerful new feature allows you to seamlessly retrieve secrets directly from your preferred secret store. This functionality is now available for Bitbucket Cloud based runners, and self-hosted runners.
To get started with this feature, you'll need to code your own middleware to let Bitbucket communicate with your third party secret provider.
Then, you'll need to configure your Bitbucket pipelines to retrieve the appropriate secrets at runtime.
If your pipelines are using a self-hosted runner, you'll also need to point that runner to your middleware.
All of these steps are detailed in our help documentation.
Key changes
Bitbucket Pipelines can now integrate with third party secret providers to allow cloud-based and self-hosted runners to retrieve secrets from external vaults at runtime.
Benefits
Improved security and compliance.
Jimi Wikman
💫 Jimi Wikman

Page previews are better than every before

Premium and Enterprise customers will see a new and improved page preview when they hover over a page title in the content tree. This preview will contain a sampling of three short sentences taken from the page, selected and ranked for relevance by Atlassian Intelligence (AI).
Because this feature uses Atlassian Intelligence (AI), it is only available to customers on the Premium and Enterprise plan. There won't be any change to page previews for Free and Standard customers.
Key changes
Premium and Enterprise customers will see a new and improved page preview when they hover over a page title in the content tree. This preview contains a sampling of three sentences from throughout the page, selected and ranked for relevance by Atlassian Intelligence (AI).
Free and Standard customers (and customers with AI turned off) will continue to see a preview of the first 250 characters of a page when they hover over its title in the content tree.
Jimi Wikman
💫 Jimi Wikman

Control Jira notifications for external users

Jira admins can now control notifications to external users. An external user is someone who collaborates with your team but has a different email address from your company domain.
External users will receive issue-related emails but with user-generated content removed. They'll no longer receive project emails and events like project deletion reminders and requests for Jira Premium features such as Plans.
To choose this option, first verify the domains in Atlassian Administration and claim the accounts. Then, to control what information an external user receives:
Go to Atlassian Administration.
Select Security then External users.
Enable the External user policy.
Internal users will still get notifications.
Jimi Wikman
💫 Jimi Wikman

Create post-incident reviews (PIR) using Atlassian Intelligence

Atlassian Intelligence generates incident summaries, which can help on-call teams save time and reduce the manual effort involved in creating post-incident reviews (PIRs). Select a relevant incident and use the AI-generated suggestions to create and finalize the PIR description. Read more about creating PIRs with Atlassian Intelligence.
Jimi Wikman
💫 Jimi Wikman

Improve issue description clarity with AI

Use Atlassian Intelligence to add clear, consistent structure to your Jira issue descriptions.
Once you have added all the details to include in your description, AI can restructure it into meaningful sections based on the issue type, including:
User story, context and acceptance criteria (for stories)
Impact, expected behaviour, and workarounds (for bugs)
* Objectives, scope, and risks (for epics).
The more detail you include in your description to start, the more complete the improved description will be.
To get started:
While editing your description, select Writing assistant.
Select Improve description.
Atlassian Intelligence will restructure your description and, when you’re happy, you can select Replace to add it to your issue.
Jimi Wikman
💫 Jimi Wikman

Editor AI: Refine command palette prompts

We're introducing a new feature to the AI command palette in Editor. The Refine button allows you to select follow-up prompts for any AI-generated response, so you can continue to generate AI-prompts within the command palette.
What's new:
"Refine" button for follow-up prompts: Easily select follow-up actions for AI responses.
Streamlined interaction: Access additional AI-generated suggestions within the AI command palette.
Key changes
Simplified AI creation: The new button simplifies selecting follow-up prompts.
Improved user interface: The preview screen now includes a more intuitive layout so you can rotate through AI-features within the command palette.
Jimi Wikman
💫 Jimi Wikman

Dedicated page for Atlassian Intelligence answers in the virtual service agent

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:
From your service project, select Project settings, then Channels & self service, then Virtual service agent.
Select AI answers.
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.
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.
Jimi Wikman
💫 Jimi Wikman

Copy product data early access program: Solving duplication of Jira entities

We're working on a solution to allow you to make decisions on how conflicting entities should be handled before copying data. We expect this to help in reducing the effort taken for post-migration clean-up. Before we make this feature generally available, we’re looking for individuals who would like to partner with us in an early access program to ensure our solution meets your needs.
Read the community blog which has steps for how to sign up for the early access program.
Jimi Wikman
💫 Jimi Wikman

Jira Product Discovery integration in Jira Plans

Jira plans are included with Jira Premium and allow you to combine work items from Jira boards, projects, and filters to create an all-encompassing plan that spans multiple teams or your entire organization.
Check out the feature documentation for more information.
Jimi Wikman
💫 Jimi Wikman

Share your plan using Smart links

Share your plan using the same Smart links you'd find in the rest of Jira. To see how your favorite sharing method might have changed, take a peek at our documentation.
Using the Share button on your plan, you can now:
share it with other Jira users or people with whom work in Slack (if connected)
embed your plan in another Atlassian product such as Confluence
export your data as a .csv file
create a static image of your plan
A lot of these were available before, but this new way of sharing them is easier, faster, and more flexible.
Jimi Wikman
💫 Jimi Wikman

Introducing ‘Request type groups’ for HR company-managed service projects

Enhance your service management with Request type groups, which enable the efficient categorization and management of HR services. This feature makes it easier for HR teams to define, organize, deliver, and report on services, enhancing visibility and collaboration within and across departments.
Similar to how portal groups are used to group related request types in the customer portal, request type groups can group related request types within a single project, improving visibility and management for the team(s) handling these requests.
For example, a request type group like ‘Employee onboarding’ might have request types such as ‘Conduct background checks’, ‘Set up payroll’, and ‘Provision hardware for new employee’ assigned to it. Here, ‘Employee onboarding’ represents the service a team or individual is responsible for, while the request types detail the specific types of work or tasks that form a part of that service.
You can use request type groups to create custom queues and use them in JQL queries to facilitate reporting across grouped request types.
To see this change, you must create a new company-managed service project using the HR project template after this feature has been released, or:
From your company-managed service project, select Project settings, then select Features.
Find Request type groups in the ‘Feature lab’ section.
Select the toggle to turn on the Request type groups feature.
Under ‘Request management’ in the left navigation, select Request types.
On the request types settings screen, you’ll see a ‘Request type group’ column in the table that displays the name of the group to which each request type has been assigned. There is also a filter that enables the display of the project’s request types by selected request type groups.
Some HR-specific request type groups will be available when creating a new company-managed service project using the HR project template. You can rename or delete these, or create your own.
To assign a request type to a group (or change the group the request type is assigned to):
Next to the request type you want to update, select More actions then in the ‘Request type group’ section, select Edit.
Make sure you’re in the Assign to group tab in the modal.
On the ‘Request type group’ field, use the dropdown arrow to display the list of available request type groups, then select the one you want to assign the request type to. Note that request types can be assigned to only one request type group at a time.
You can create a new request type group by entering the new group name into the field, then selecting Create “name of group”.
To remove the group the request type is assigned to, select the cross next to the group name. If no group is selected, the request type will be ‘Unassigned’.
Select Done.
To manage request type groups:
On the request types settings screen, select More actions for any request type, then select Edit in the ‘Request type group’ section.
Make sure you’re in the Manage groups tab in the modal.
To add a new request type group, select Create request type group at the bottom of the modal. Enter the name of your new group, then select the check icon.
To rename a request type group, select the name of the group you wish to edit, make your changes then select the check icon.
To delete a request type group, select Delete next to the group you wish to delete. You’ll see a message showing the number of request types that will become ‘Unassigned’. Select Delete to proceed.
When you’ve finished editing your groups, select Done.
To turn off this feature:
From your company-managed service project, select Project settings, then select Features.
Find Request type groups in the ‘Feature lab’ section.
Select the toggle to turn off the Request type groups feature.
Jimi Wikman
💫 Jimi Wikman

Smart link embed view now available for Jira Cloud releases

Smart link embed support now extends to Jira releases. No more clunky screenshots. Just copy, paste, and configure views of your Jira releases seamlessly in Confluence.
Select your release: Head over to your Jira releases. Select the release you want to embed, then copy the link by copying the URL from the navigation bar at the top of your screen.
Customize your pages: Navigate to your Confluence page and paste the link — it will automatically embed the release view. Then, tailor the page to suit your needs. You can change the size of the embed as needed.
Share and collaborate: Spread the word! Share your Confluence page with your team and stakeholders where they can comment and provide feedback directly in Confluence.

Jimi Wikman
💫 Jimi Wikman

Version history now available for whiteboards

You can now view and restore previous versions of your whiteboards, giving you greater flexibility and control over your whiteboard content.
To view a whiteboard’s history, open the whiteboard’s ••• menu in the top right and select History.
From there, you can view previous versions of the whiteboard, and if you want to restore one of them, you can create a new whiteboard using that version’s content. Permissions on the new whiteboard will be the same as the original.
Jimi Wikman
💫 Jimi Wikman

View recent links from Smart Link hover cards

You can now view relevant documents, pages and other work items straight from Smart Links.
To view recent links:
Hover over an inline Smart Link.
Select View recent links.
The modal that opened will show you documents and work items:
found in the link
where the link is inserted
Jimi Wikman
💫 Jimi Wikman

Updates to filter name searches

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.
Jimi Wikman
💫 Jimi Wikman

Epic Link and Parent Link changes no longer show in the audit logs

As part of our larger stream of work towards deprecating the Epic Link and Parent Link fields (which you can read about in our documentation as well as our updates in our Community space), changes to these fields no longer generate a change record. On issues, this means that changes made to the Epic Link and the Parent Link no longer show in the issue's History tab.
Changes to these fields are also no longer being communicated via the API, which we announced in the developer community.
Jimi Wikman
💫 Jimi Wikman

Space details now have a modernized look

The space details settings page now has an updated modern look and have been consolidated from two pages down to one.
Space admins can now edit the space name, key, description, and home page with fewer clicks. The list of Admins is now identified with profile pictures instead of full names.
We have also provide localization for dropdown options that were previously untranslated.
To get started with this change:
Confluence space administrators can:
Go to a space
Select Space settings on the side nav
Under the General card, select Settings
Key changes
Key changes:
URL is updated from /wiki/spaces/viewspacesummary.action?key=CFE to spaces/<spaceKey>/settings/details
It is no longer two pages, it is now one form
the list of admins are gone, it is now represented using icons
Dropdown options are now i18n’ed (previously not translated
Jimi Wikman
💫 Jimi Wikman

Improve the clarity of issue descriptions with AI

Use Atlassian Intelligence to add clarity to your issue descriptions. Quickly improve your descriptions with clear structure and headings so they’re easier to read.
To get started, while you’re writing an issue description:
Type / in the issue description field, or select the Atlassian Intelligence button.
Type or select Add structure.
Using AI, we’ll generate a new, structured issue description for you to review. Look over the new description, and choose to replace your existing description or add the new one underneath.

Jimi Wikman
💫 Jimi Wikman

Update the request type when moving issues

When you move or bulk move issues to different projects or issue types (or migrate an issue type out of a project), you can now select the new request type during the move. We're excited to release this much-requested update to make issue migration simpler in Jira Service Management.
Jimi Wikman
💫 Jimi Wikman

Upcoming change to the data export rule

Data security policies allow you to use rules to control how users, apps, and people outside the organization interact with content in Confluence and Jira.
We’re extending the data export rule to also block the downloading of files attached to Confluence pages. After this rule takes effect, users will no longer find a download button in sections like the attachment list, macros, and file previews.
We opted to extend the data export rule rather than introduce a new one because of the considerable overlap between export and download. Our findings showed that the types organizations needing to block exports also wanted to prevent attachment downloads.
This change will affect any existing policies that have configured the data export rule to block exports. At this stage, it will not block attachment downloads in Jira.
To check whether your data security policies currently block exports:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Data security policies.
Select a policy, and check whether exporting data is blocked.
The data export rule requires Atlassian Guard Standard.

Jimi Wikman
💫 Jimi Wikman