Jump to content

Jimi Wikman

💫 Owner
  • Joined

  • Last visited

  1. The new process to renew certifications is now available. This approach encourages ongoing learning and Atlassian Community engagement. Certification holders (candidates) can now start using continuing education (CE) units to renew their certifications. CE units can be earned by completing courses on Atlassian University, and/or attending a webinar from Atlassian’s Live Learning Program, or watching the recording if you are unable to attend. CE units can also be earned by attending Atlassian events - either a local ACE or a global Atlassian event, either in person or virtually.
  2. Use the audit log to see key activities such as when a dashboard, chart, data source, or data share is created, edited, or deleted. Read more about tracking activities from the audit log To see audit log activities for Atlassian Analytics: Go to admin.atlassian.com. Select your organization if you have more than one. Select Security > Audit log. From the Product filter, select Atlassian Analytics. The audit log will show all tracked activities for Atlassian Analytics in your organization.
  3. Feast your eyes on our new look and feel that's now applied to the summary screen.
  4. View and access previous pipeline runs directly in the UI to help you more readily diagnose any issues that may have occurred while running the pipeline. We are releasing this feature incrementally - 10% on January 13, 2025, 50% on January 14, 3025, and then released to 100 % of customers on January 15, 2025. On the Pipeline result page for a specific pipeline, you'll see the Runs dropdown (if there were previous runs for that particular pipeline) that will display a list of these previous runs when selected. Select a run from the list to access and review the information associated with that previous run. We have also added the run number into the URL. So, when you are viewing a previous run, you can easily save and share a link directly to it. Note: The previous pipeline Runs dropdown will not show up if you re-run an entire pipeline. This is because when that happens, it creates an entirely separate pipeline, rather than an additional run on an existing pipeline.
  5. Admins can now set their Company Hub as the default landing page for Confluence, replacing the default Confluece home page. If you are a Confluence product admin, select Confluence administration (gear icon in the upper right). Then select Configuration > General configuration and scroll to Confluence landing page. Use the dropdown menu to select your hub, the default home page, or a space's Overview page as the default landing page for all users. Users can now access this page by selecting the logo in the nav bar or by navigating to [your domain].atlassian.net/wiki/.
  6. Users can now be notified when they are mentioned in Confluence databases. Collaborate more seamlessly by ensuring the right team members are in the loop on work. Disable mention notifications by unchecking Send notification to mentioned user in the User field settings.
  7. We’ve made improvements to how fields display in custom tabs on the issue view. Previously when configuring a request type in Jira Service Management, if a field was added to both the request form and to a custom tab when configuring your issue layout screen, it would always display on the issue view as part of the request form - not inside a tab. Now these fields will always display in the custom tab in the issue view, honouring the configuration of your issue layout screens. Read more about adding fields to custom tabs on issue view
  8. The issues for attention insight on Jira Service Management boards surfaces your 30 highest priority issues, making it easier to find and address important work. You can now see issues that have breached, or are within 30 minutes of breaching their Service Level Agreements (SLAs) alongside any stuck and blocked issues so that you and your team know what to pay attention to next. Find out more about the issues for attention insight. Select Views in your project navigation, then select the Board tab, then select the Insights button to see your issues for attention. If you don't have Views in your navigation, or don't have boards enabled on your project, an admin can enable them from the Features page in your Project settings.
  9. Update the priority of Jira issues straight from Smart Link list view. What is Smart Link list view? While viewing Jira issues in Smart Link list view, select the priority from one of the items. Once the dropdown appears, you can update the priority straight from the cell.
  10. Use the power of Atlassian Intelligence in Confluence whiteboards to summarize the content on your whiteboard, generate new ideas, and group similar content. To see how you can use each of the features, view instructions for AI in whiteboards.
  11. Update the status using a Smart Link list view without the need to open the Jira issue. What is Smart Link list view? While viewing Jira issues in Smart Link list view, select the status from one of the items. Once the dropdown appears, you can update the status straight from the cell.
  12. 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.
  13. With the new import experience, you can easily transfer information from CSV files into Jira Service Management, saving time and effort. To import data into a new Jira Service Management project from a CSV file : Select Projects > Create projects > Import data on the sidebar. Select CSV to use any CSV file to import your data.
  14. We're excited to introduce a new feature that allows you to save time by copying only the specific Jira Service Management (JSM) projects you need to your sandbox. This enhancement streamlines the setup process, ensuring you have exactly what you need without unnecessary clutter. Additionally, audit logs now track the copying of specific projects, providing a clear record of changes for better management and oversight. Understand how to select data to copy To copy specific Jira Service Management (JSM) projects from your production to its sandbox: Go to admin.atlassian.com. Select your organization if you have more than one. Select Products > Sandbox. Under Actions in the product table, select Copy production data. Select the Specific Jira Service Management projects. Follow the prompts to copy data into your sandbox. Learn about what we copy to sandbox