nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How does "Curated definitions in Jira" work?

Kevin Paugam

Hi everyone,

I am trying to understand the impacts of using new functionality to edit AI-generated definitions in Jira.

Indeed, from the change description provided here, it is difficult to understand who is allowed to change these definitions, and how changing definition affects results for other users.

When trying the functionality, I can see that you can choose "Restricted to anyone on this project" or "Restricted to Anyone on this site". Does it mean that Atlassian Intelligence will provide only the curated definition for the given project or site? And what happens if someone else changes the definition afterwards? How is it decided which functionality if the most relevant one?

IMO, changing definition at site level should be authorized only to Site admins, whereas changing definition at project level should be authorized only to Project admins.

Comments

Izzy Kohout

Hello @kevin , thank you for your question and the feedback!

I'm Izzy, the PM looking after our AI definitions feature.

I can confirm that currently all users are able to edit definitions. After they've edited a definition, it will be attributed to them on the definition (there will be a message that says 'last edited by XYZ name'), and also a full edit history to give admins more visibility.

Screenshot 2024-10-07 at 3.27.09 PM.png

The visibility restrictions describe how far the definition persists. So a user edits the definition and select 'anyone on this project', the edited definition will only show up for that term in the current project. If you select the site-wide option, it persists site wide.

If someone changes the definition afterwards, the most recent edit will override. All edits will remain visible in the edit history.

Thank you for the feedback regarding clarity - we try to make sure our documentation and in-product messaging is as clear as possible, so we appreciate your help in making it better!

Let me know if you have any additional questions!

Best,
Izzy

Erin Trahan

Hi @Izzy Kohout

We have some users interested in the 'define' feature at our org, specifically so that on Jira tickets our acronyms and terms will be more standardized across the company. However, the idea that any user can edit definitions is worrying, rather than just site/project admins. Are there any plans to add restrictions in the future?

In addition, is there a place to see these user-created definitions in one place, like a glossary space on Confluence? If we go forward with using this feature in more projects I'd like to be able to see exactly what words our users are defining, and having them all in one place would make it much easier to ensure the definitions are correct. (Also, it would be great if user-defined words would always be underlined like the AI-suggested ones!)

Thanks!

Izzy Kohout

Hi @Erin Trahan thank you for the questions!

We're still refining permissions for the definitions feature, so your feedback will definitely be taken into account. Currently the behaviour is that all users can edit and correct definitions.

Your idea for a centralised glossary is a great one and something we are actively exploring. I can't share anything concrete yet, but I'd love to speak to you F2F about how we could build something useful for you and your teams in this space if you're interested?

If so, please feel free to email me at ikohout@atlassian.com and we can set up some time!

Welcome!

It looks like you're new here. Sign in or register to get started.