
Content below curated and copied from Atlassian release notes for our production environment.
Confluence Updates
Improved templates experience
When using the template browser, you can now select (or de-select) multiple categories as filters. We have also introduced two new categories: Featured and My Templates.
Open a blank page by selecting the Create button in the top navigation. The template browser will open on the right.
The template browser will disappear as soon as you start typing. If you
need to change templates, you can open the browser again: select Templates & import doc from the more actions menu (...) in the upper right.
Jira Updates
Issue search: More fields and improved design
We've improved the way you search for issues:
Search for issues based on Creator and Affects versions without using JQL.
Save space when expanding the Labels and Fix versions fields.
Use groups to search for issues related to multiple users at the same time with fields like Assignee, Reporter, and Creator. If you select a group, the search will match issues to all users in a group.
Custom navigation colors are now compatible with dark theme
If you've set a bright custom color for your navigation bar, we'll automatically modify it for anyone in your site using dark theme.
Your work suggestions panel in Jira has new updates
We've made a few subtle design changes to improve the overall look of the panel where you can see what to work on. The most noticeable change to you will be that all the cards are now selectable.
Go to your Jira board and select your avatar. A panel will open with What to work on suggestions. Select any card you would like to see more information about.

Move sprints to the top of your backlog with a single click
We’ve heard your feedback and agree that re-organizing sprints in the backlog could be a lot easier. That’s why we’ve added the ability to move a sprint straight to the top or bottom of your backlog. This will save you some time (and a lot of clicks!) when planning work for your team.
To try it out, go to your backlog and find the sprint you’d like to move. Select more actions (…) then Move sprint to top. To move a sprint to the bottom instead, select Move sprint to bottom.
Quick search: Filter by label
We've added a label filter to quick search, allowing you to further refine your search results and quickly find the work you need. Learn more about using quick search
To filter your results:
Select Search in the navigation bar (or press / on your keyboard).
Type your search query.
Use the Filter by label filter to find and select the label you want to see results for.
Introducing approvers for releases
Make sure the right people have signed off on your release by adding them as an approver.
Approvers can approve or decline a release, and add a reason to a decline so you know what needs to change.
Approvers now join drivers (the person responsible for coordinating the release from start to finish) and contributors (people who need to complete related work) to make your release process smoother. These roles help you build good communication habits and define clear responsibilities with your team.
To get started with approvers:
From your project’s sidebar, select Releases.
Select a release from the list.
In the Approvers section, select Add approver (+).

Make quick edits to cards on the board
We’re rolling out a new feature that allows edits to be made directly to cards on the board without needing to open them up into a full screen view.
The 4 fields that are currently rolling out with this functionality are: summary, parent (epic), estimate, and assignee. Just click on the field you’d like to edit and it will become editable, there’s no preparation needed.
Key changes
Summary, epic, estimate, and assignee are now editable fields directly on the board view.
Just click on the field you’d like to edit and it will immediately become editable.
To click and drag cards you’ll need to click on empty space that isn’t one of the editable fields.
Benefits
Only one click is required to start editing the summary, epic, estimate or, assignee from the board view.
Since you don’t need to open the issue into a full screen view, edits can be made in context of the other items on your board. Which can help with things like sizing items in your sprint.
We’re bringing shared experiences across Jira, we’ve seen massive uptake of editing issues directly from the backlog without opening issues so we’re bringing that same capability to the board view.
Jira Service Management Updates
JSM Introducing customer notification logs
Using customer notification logs in Jira Service Management, project admins can easily find out which notifications weren’t received by their customers and take necessary actions to ensure that their customers get notifications on time.
To access customer notification logs, go to your service project, and select Customer notification logs. Here you’ll find details like the name of the notification, when it was sent, and why it wasn’t delivered.
Currently, we’re introducing logs for customer invite notifications only. For more details, see this community post.
Learn more about customer notification logs
Atlassian Fast Facts
Tips and information for WashU Atlassian users.
Comala Boards for Confluence
Comala boards are useful for visualizations and use drag and drop functionality in Confluence Cloud. Below is an example used for a SWOT analysis. Other uses may include a project roadmap or a retrospective.

Refer to Comalatech’s user guide for Confluence Cloud to learn more.
Use Jira Cloud’s enhanced search
The Jira search bar in Cloud shares quick links to all Issues, Boards, Projects, Filters, Plans, and People. It is a great way to find what you’re looking for without too much effort in a new environment.

On this page:

Content below curated and copied from Atlassian release notes for our production environment.
Confluence Updates
Customize starting numbers for numbered lists
We are rolling out a feature that enables you to have more control over numbered lists in the editor. You can now initiate numbered lists from any custom starting number. This functionality makes it easier to intersperse numbered lists with different types of content while maintaining a coherent numbering sequence.
Here's how to employ this feature.
Starting a Numbered List from a Custom Number:
In the editor, type a number followed by a period and a space (for example, "7. ”) to begin the list from that number. The list will increment from this number onwards.
Breaking up a Numbered List:
Position your cursor at the end of a line item in an existing numbered list and press 'Enter' twice.
The list will keep its logical numbering, but note that adding items to the first part of the split list will not automatically update numbers in the second part. The starting number of the second part must be manually adjusted if needed.
Updating the Starting Number of an Existing Numbered List:
Move your cursor to the start of the line item and press Backspace.
Type the new number followed by a period and a space (for example, "8. "). This will convert the item to a numbered list starting from the new number.
This feature allows for more flexibility and better content organization in your documents.
Transfer of page ownership between users
When a page is created, the person who creates is now known as the owner of that page. We've made it possible for page owners to transfer ownership of their page to another person at any time. Space and site admins can also transfer page ownership from one user to another.
This way, if a current page owner leaves a project, team, or company, ownership of the page can then be granted to whomever is most appropriate, and maintenance and validity of the page remains fresh.
A page owner is the ‘point person’ for a given page and their name appears in the byline, under the page title.
Learn more about page ownership and how it can be transferred
Transition Jira Issue Status with Smart Links
No more having to switch between Atlassian products and open Jira whenever you want to transition an issue - now, you can transition Jira issues directly from smart links in Confluence.
To transition a Jira issue in Confluence:
Open a Confluence page and insert a link to your Jira issue, by either pasting it onto the page or searching for it in our CMD+K menu. This link will automatically become a smart link.
Click on the smart link and select Card view from the toolbar. You'll now be able to see the status of your Jira issue in the card.
Click on the status modal and select the new status you want to update your issue to. This update will be visible on the Confluence page and the Jira issue.
Learn more about transitioning Jira issues with Smart Links in Confluence
Jira Updates
Changes to epic fields
We've made changes to epics on your board and backlog to more closely align epics across company-managed and team-managed projects.
Epics on your board and backlog will now display the epic’s Issue summary in their lozenge and on the epic panel. Additionally, the epic color on the board and backlog will now use the epic’s Issue color.
These updates will also apply to the Epic link field in the issue view. Learn more about these changes
Update to the create issue mini window
We've updated the look and feel of the create issue mini window.
Next time you're creating an issue, you can use the icons on the top right of your issue to exit full screen and use the re-designed mini window. You can also click the background outside the issue you're creating to exit the full screen view.
With the mini window, you'll be able to create work in context and navigate your project without losing progress on your new issue.
Increasing the visibility of the create issue mini window
We want to help people discover the new create issue mini window, which has recently been re-designed. We’ll open the mini window by default the next time you create an issue.
It’s easy to switch back to full screen with the icons on the top right of the mini window. We’ll remember the state you prefer for the next time you create an issue after that.
However, we encourage people to try using the mini window. It has significantly more flexibility than the full screen window as you can move around your instance and interact with other issues without losing progress on the issue you're creating.
Key changes:
The next time you use the blue "Create" button to create a new issue, instead of the full screen window (that you're probably used to seeing), a mini window will open at the bottom of your Jira.
Whatever state you're in when you finish creating that issue will be saved as your preference, so we'll make sure to open the right window for you in the future.
You can switch between the full screen and mini window quickly by using the icons on the top right of the create issue window.

Benefits
Move around your Jira without losing progress on your new issue.
Interact with other issues to copy/paste information and get the context you need while creating a new issue in the mini window.
Pause creating your new issue (even minimize it to revisit it later) and continue using your Jira as normal without needing to open a new tab.
Company-managed projects: New and improved context menu in the board and backlog
We’ve refreshed the contextual menu for issues in your board and backlog. Related actions are grouped together so they’re easier to find, and you can now open the menu by right-clicking on an issue.
View the contextual menu by going to your board or backlog, and right-clicking on an issue.
The project 'Roadmap' is now called 'Timeline'
We've changed the name of the Roadmap view in Software projects to Timeline. This change will be reflected in your project sidebar and on the view itself but does not impact the functionality. The Timeline continues to be your home for planning work, tracking progress, and mapping dependencies.
Timeline Toolbar Legend
If you've ever asked "What does that symbol mean?" when viewing you project timeline, then we have a feature for you! Introducing the timeline legend, a revolutionary new feature that shows you what all the icons mean.
Select the i in the bottom right of your timeline (next to the weeks/months/quarters toggle) to see a handy guide to the symbols on your screen.
This same feature has also been released in Advanced Roadmaps.

Show and hide sections in the releases feature
We've heard some people like more space to look over related work or issues for their release. So we've made the release description, related work, and issue sections collapsible.
That means you can hide one section away so the others get more room (or hide them all at once, we won't judge).
To get started:
From your project's sidebar, go to
Releases.
Select a release from the list.
Next to the section's name, select the chevron to show or hide that section.
Improved attachment management on issues with over 150 attachments
We’ve improved your experience when dealing with issues that have large numbers of attachments.
Now, when an issue has over 150 attachments, attachments will be automatically displayed as a list.
In this list view, you’ll be able to upload and delete attachments, download a single attachment, and download all the attachments on the issue at once.
Learn more about adding attachments to issues.
Restore invalid issue types
If there’s a request type with an invalid issue type in your project, you can now restore the issue type from the Request types page in your Project settings.
When you select the invalid issue type, we'll let you know which issue type was previously connected to that request type. Select 'Restore' to add that issue type back to the request type.
Quick search: Spelling suggestions
We're improving how you find work in Jira by introducing search suggestions in quick search. Now, if a query seems incorrect or misspelled, quick search will suggest corrected or alternative spelling for your search.
Learn more about using quick search
Jira Service Management Updates
SLA success rate will be 100% for time periods when no issues are created
Thanks to feedback from customers, we learned that the SLA success rate is currently reported as 0.0% for time periods when there are no issues created which isn't the expected result.
Now that we've fixed it, the SLA success rate for time periods when no issues are created will be reported as 100% instead of 0.0%.
Attachments now available in forms
Collect all kinds of attachments from your customers using the new attachment field in forms. Attachments can be documents, images, or video files.
Your customers can browse to upload files when filling out this field in their form.
These attachments will appear both in the form itself for full context, and under Attachments in the portal and issue view with all other attachments for quick and easy access.
Learn more about how fields work in forms.
Added new variables for canned responses
We’ve added two new variables - Request URL and Portal URL that you can use while creating canned responses. The details of these two variables are as follows:
Request URL - The URL of the request in the portal.
Portal URL - The portal URL, which can be seen on the Portal settings page.
Learn more about using variables in canned responses
Atlassian Fast Facts
Tips and information for WashU Atlassian users.
Manage Notifications
To review your Confluence notification settings:
Open and log into Confluence.
Select your Initials or Avatar in the top right corner of the screen.
Select Settings.
On the Settings tab, select Email under Your Settings.
Adjust your email settings to match your preferences.
Select the Watches tab to review spaces and pages you are watching and select Stop Watching for any items you would like to omit from email notifications.
To Convert or Not to Convert (to the Confluence Cloud Editor)
How do you decide whether to convert?*
Use the preview function in the conversion process to see what will convert.
Determine whether you have the time to make necessary changes to the converted page(s).
Convert the page. You can always return to the legacy editor later. (See the document linked below to learn more.)
*Confluence Cloud Editor conversion is not required.
If you choose to convert your page(s), there are some best practices for conversion. Consult this document in Box for instructions.
Enhance your Jira Search through JQL
Enhance your Jira search capabilities through Jira Query Language (JQL). Watch the video below to get started with JQL:
On this page: