Josh Sherwood Atlassian Team

Hi @Spencer Hudson Thanks for reaching out, and I apologise for the hassle while we update all our materials. I've checked with the team that looks after those learning docs, and these should be all updated and completed by the end of January.

@Darryl Lee Hi Darryl, apologies for the delay getting back to you. I can confirm that the Release Tracks date of December 9th is still accurate. @Shy Hi Shy. Last year, we announced that we were updating Jira's language to better reflect the diverse ways teams define and manage their work, whether they're a software team,…

@Andriy Kozynets Apologies, Andriy. It appears that some UI references to 'project' were missed during the updates. Thanks for highlighting these, I've passed it on to the team and they'll be fixed shortly. @Susan Hauth _Jira Queen_ @Trevan Householder_Isos-Tech-Consulting_ @Alexander Smotrov Thanks for sharing your…

@Jacob Ebenhoe Hi Jacob. No functionality has changed as part of this update, so you should still be able to create your Boards. Just keep in mind that multiple and cross-project boards are only available in company-managed spaces (team-managed has never had this functionality).

@Bill Sheboy @Anne Saunders @Trevan Householder_Isos-Tech-Consulting_ Thanks for sharing your feedback. We understand your concerns about the misalignment of API and JQL updates with this change. This decision was influenced by complexities that would have impacted our release timeline, and we wanted to introduce more…

@Leo Mazzi Thanks for your feedback. There are no current plans to update the REST API endpoints. We'll keep teams informed of any changes if and when they occur. @Shelby C These updates will be rolled out to the above timeline based on the highest edition of the products you have. So, if your team uses multiple Jira…

@Jamie Echlin _ScriptRunner - The Adaptavist Group_ @Joerg Sorry for the inconvenience here. Our team is aware of the issue with the banner and is looking into it. @Afsheen Sabir this doesn't appear to be related to these terminology updates. Please contact our support team for assistance.

@Ondřej Medek thanks for raising this. We're aware of some terminology inconsistencies in our admin experiences, particularly regarding the permissions you mentioned. Our team is actively working on addressing this issue, and updates to these permissions should be made soon. cc: @Pavol Sočuvka

Hi @Jaden Minix thanks for reaching out, and apologies for the delay in responding. Our priority is to enhance the overall product experience in Jira for all teams, which involves considering the broader use of our tools and their diverse user base. This update is part of a wider set of changes on our roadmap aimed at…

@Carla Ann K. Rowland: there are currently no plans to extend this update to Jira Data Center. @Russell Zera: this update can be found on the Cloud Roadmap here.

@Jon Myhre @Nicolas Desessart Danish and French will both keep their current terms.

Hi @Jon Myhre I've added some detail to the FAQ on the progress of the rollout: These updates have now been rolled out to sites on our Free and Standard plans. We'll begin rolling out this change to sites on our Premium and Enterprise plans from April 14, 2025. Customers on release tracks will see these changes in-product…

@Carlos Andres Lopez Ayala apologies, this was an error. Connectors will continue to use "Issue Type" for the moment. We will provide updates for any changes in the future.

@Bill Pruett I'm sorry you're unhappy with the new terminology. As this is currently rolling out, there's no way to opt out or vote on this change. In the future, we'll be moving towards using the language you use for your work types more prominently within Jira, which should provide a more tailored experience for you and…

Hi @James Our team conducted research to determine how best to implement these changes across the various markets supported by Jira and to assess whether updates to the language were necessary. As a result, the following languages will have updated terminology to reflect this change: Chinese (Simplified), Chinese…

Hi @David Friedrich, Thanks for sharing your feedback. I understand your frustrations with the direction we’re taking, but I want to assure you that this decision wasn’t made lightly. 1/4: You're correct that "issue" is deeply ingrained in how teams work. However, we've heard for years that it has posed challenges for…

Hi @Samuel Segaud - there are no changes to automation smart values at this time, they'll continue to use {{issue}} terms.

@Yatish Madhav These updates have begun and will progressively roll out to all instances throughout March and April. These updates are not specifically coordinated with the navigation changes, so you may see them at different times. For customers on release tracks, we'll provide more detailed information about specific…

Hi everyone. I've updated the FAQ to address some of the questions regarding the impact on APIs and JQL, as well as provide more details about the rollout. Next week, we'll post an update on our Atlassian Developer Community that will offer more detail. I'll share the link once it's available. Q: How does this change…

Hi all. Thanks for sharing your thoughts and feedback. I understand there are some frustrations with the direction chosen, and I want to assure you that we've taken time to carefully consider customer feedback from various channels, including the discussion in the previous blog post, insights from our Chrome extension, and…

Hi @Chris Speier. Is your product using release tracks? If so, you may not see this update for a couple more months, as it will be bundled with a number of other updates and rolled out at same time.

Hi @Chris Speier – all Jira users should now see this updated in their Software projects.

Hi @Chris Tetzlaff – unfortunately, the opt in/out experience is no longer available as this feature has begun rolling out. If you only have Planning features enabled, you won't see the categories in the sidebar. Apologies that I can't be of more help here.

Hi @Chris Tetzlaff – just to clarify, is it the sidebar categories mentioned in this blog that you're referring to?

Thanks for your feedback @Nick – we're hoping that the collapsible sidebar categories are a step in the right direction for allowing users to simplify their sidebar and hide the items that they don't regularly use. But, we understand that there's still a lot more that can be done. We'll be monitoring feedback around this…

Thanks for your kind feedback @kasper - we'll definitely be looking into improving the experience around adding apps in the sidebar as part of our ongoing explorations. I'll make sure to pass on your feedback around Components and the Confluence integration.

Hi @Larry Johnson Along with apps, we're also looking at how we might improve the experience of adding shortcuts in the sidebar – so your feedback is really valuable here, thank you. I'll also make sure to pass on your feedback around Issues and Components not being able to be toggled off in company-managed projects.

@Jack Brickey Sorry to hear you aren't seeing the opt-in in your instance. If you're still having difficulties, feel free to email me the details of your site and I can check with the team why this might be.

Hi @Bill Sheboy – nice idea on allowing users to pin items. Will take that to the team, and we'll look at that option as part of our future explorations. Thanks for the feedback.

Hi @Chris Buzon. Add-ons and apps are definitely things we're looking into as part of our explorations, and we're aware that they they can cause a lot of clutter for many users. Thanks so much, appreciate the feedback.