Confluence Updates

Space Admin Mission Control

Space admins can now use Mission control in Confluence!

This change allows greater access to analytics and space management capabilities. It also allows site admins to dig deeper into information at the space level.

To access Mission control:

1. Select Space settings in the left navigation bar.

2. In the new Monitoring and tools section, select Mission control.

3. View the dashboards and info in the Activity and Content management sections.

Atlassian AI Updates in Confluence

Catch up quickly with page comments summary

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.

Open

Introducing content generation with richer context

Get smarter content creation with the AI-powered features in the Editor! With this update, you can now access information from your Jira and Confluence instances. Just share a link, and the AI will use data from these sources, making your content creation more insightful and comprehensive.

• Smartlinks: Use Smartlinks to seamlessly integrate information from Confluence pages and Jira issues. Simply paste a link, and the AI will automatically consider the content when crafting your prompt.
  Try: Give me a tl;dr about this project.

• Content summaries: Get AI-powered summaries of articles, comments, Jira tickets, and Confluence content. This can help you quickly understand complex topics and extract key insights.
  Try: Summarize the work that has been done on this ticket.

• Comprehension assistance: Leverage AI to translate user stories into technical content, highlight important points in documents, group fragmented information, and map relevant details. This streamlines your workflow and saves you valuable time.
  Try: List all the open action items from this page.

Embed your Jira dashboards in Confluence

You will now be able to copy a link from a Jira dashboard and paste it into Confluence as a smart link embed. This makes it easier to share your Jira data with other Confluence users.

Quick react from Confluence comment and mention notification emails

We've added emojis directly to comment and mention notification emails, allowing you to easily engage collaborators with a quick reaction. With a simpler reactions experience contextually available, users can reduce tool-switching by reacting directly from the email.

Comment on whiteboards for further collaboration

The commenting experience will now be available in whiteboards, alongside pages. Leave comments, @mention teammates, reply to conversations, and more with comments in Confluence whiteboards. You can see mentions and replies directly in your notifications.

Switch to comment mode in a whiteboard by selecting the comment icon in the toolbar on the right or use M on your keyboard. Once you're in comment mode, click anywhere on the whiteboard to create a comment.

Jira Updates

Jira Plans warning filter update

Your planning tool warnings center is now updated with a condensed list of settings you can switch on.

Open

We're also moving the “Filter issues with warnings” toggle from inside the Warnings dropdown menu to the Filters dropdown menu, so you can see all the details there.

Timeline Updates

See how your issues relate to each other in the timeline

We’ve made it easier to see the relationship between parent and child issues in the timeline.

In the timeline, all child issues will now appear under their parent issues so you can better visualise how your work relates to one another. This feature was previously only available with subtasks and their parent issues.

You can also now create child issues for any issue type (except subtasks) in the timeline.

To create a child issue from the timeline view:

1. Select Create child issue ( + ) in the row of the issue you’d like to create a child issue for.

2. Enter a summary of what needs to be done for this child issue.

3. Select enter on your keyboard to create the task, or escape to cancel.

As an added bonus, we’re increasing the number of child issues you can see in the list view to 500 so you can see even more of your work at once.

Drag and drop to reparent issues

We’ve made it easier to reparent issues in the timeline and list views.

We’re slowly rolling out this feature, so don’t worry if you can’t see this yet.

In the timeline and list views, you can now reparent a single issue by simply dragging and dropping it underneath a new parent issue.

The team field in Jira issues now shows the team icon

Previously, selecting the team field in an issue would prompt a search displaying the singular "Person" icon. The correct "Team" icon now shows to indicate what should be selected for the field.

Find your attachments even faster

We’re introducing new filters so it’s even easier to find the attachment you’re looking for.

*We’re slowly rolling out this feature, so don’t worry if you can’t see this yet.

If this is already available for you, you can now use brand new filters in Attachments to find a specific attachment.

You can filter attachments by:

• who added them

• the type of attachment (image, document, spreadsheet, and more)

• the date it was added to an issue

More about using filters to find attachments

Updates for editing and managing issues

Change the status of multiple issues

From the backlog, you can now transition up to 1000 issues, even if they have different workflows. For example, you could transfer 10 bugs from In progress to Done and 10 tasks from To do to In progress.

We’re still working on improvements for this feature. At the moment, you’ll only be able to move issues to statuses that don’t require a transition screen.

To start changing the status of multiple issues:

1. Select multiple issues from the backlog.

2. Select Edit.

3. Select Status.

Heads up when you hit 5,000 issues on your board + backlog

View, edit, and interact with your board and backlog — even if you've reached the 5,000 max issue limit.

This means your board admins get a heads-up to adjust the board filter, and teams can continue to work as usual.

To adjust the board filter, navigate to More [...] > Configure board.

Scroll to the Board filter and adjust what's included and excluded using Jira Query Language (JQL).

Introducing limits to how many items you can add to an issue

To enhance the reliability and efficiency of our platform, we’re introducing new limits to how many comments, attachments, and links you can add to an issue.

Easily control the visibility of work suggestions in Jira

We're adding a "Turn off work suggestions" link to the Work suggestions panel footer to let you easily find the Work suggestions toggle under the View settings menu. When you turn the toggle off, you'll no longer get any suggestions, and the work suggestions panel won't open when you select your avatar on the Jira board.

You can always turn Work suggestions on at any time from the View settings menu to start getting suggestions again.

Read more about Jira work suggestions

Copy and share a link to your Jira dashboard

We're adding a "Copy link" button to let you share your Jira dashboards in other Atlassian products, such as on a Confluence page, whiteboard, or database. These links can be displayed as a card in Confluence to make it easier to share your Jira data with others.

Finish setting up your development tools from the issue view

Jira site admins can now finish setting up code and deployment tools by following a link from the issue view. If any site admin has installed a tool on your site, we'll show a link on the development panel so you can finish setting it up.

If a code tool has been installed but not configured, we'll show a link to Set up code tools.

If a deployment tool has been installed but not configured, we'll show a link to Set up deployment tools.

To get started:

1. Go to your Jira project and open an issue.

2. In the development panel, select Set up code tools (or Set up deployment tools).

3. In the dropdown, select the tool you want to set up.

4. Follow the steps to finish setting up your integration.

JSM Updates

Internal note visibility restrictions

Soon you’ll be able to restrict the visibility of internal notes based on your project roles and groups.

Sometimes, teams need to hold private discussions about customer requests, and in the case of particularly sensitive topics these discussions may need to be confidential between only a few team members (such as those in your HR or Legal teams).

With the ability to restrict the visibility of internal comments, you can now continue those confidential discussions on the issue itself, without having to transfer to email or use other tools to keep the information private.

To set the visibility for internal notes, navigate to an issue and open the issue view. Find the comment section, and start creating an internal note. Then, select the Comment visibility button. Select which group or project role you’d like to restrict this comment to. Now, save your comment.

Only the comment creator and users added to the selected group or project role will see this comment once it’s saved, meaning you can continue to work knowing your confidential request information will stay private to you and your team.

Find out more about project roles in Jira Service Management, or learn how to create and manage your groups.

Updates to AI issue triage feature

We've made some minor UI updates to the AI issue triage feature. Issues that can't be updated are now grouped together to allow for easier scanning and comprehension at a glance.

Atlassian Fast Facts

Tips and information for WashU Atlassian users.

Use Confluence AI to Define WashU Terms and Acronyms

Simply highlight the term on a confluence page and choose Define.  A list of page references will also appear.  See it in action below:

Epics, Components and Labels in Jira explained

Explore this 2-minute video explaining the differences between using structured containers (Epics and Components) and unstructured Labels to categorize Jira issues.

On this page: