You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
we got access to the AI feature in Confluence&Jira and are playing around with it on our sandbox. We are really impressed with the results. But we are missing some features or still have some questions.
Are some reasons why we are not rolling it out to our production system yet.
Hi Jonas, appreciate you sharing your questions here! I'm on the team responsible for AI in the editing experiences across our platform. To answer your 2nd and 3rd questions, they both stem from similar limitations at the moment.
Currently our AI features in the rich text editor are only aware of the content contained within the editor. i.e. the content contained within a Jira issue description, a Jira issue comment, or the Confluence page you are currently editing. So if there is no content in the Jira issue description/comment you're editing, there will be no content to summarise. See this video for more details on how it works in practice. (note this feature is distinct from the comment summarisation feature for Jira Service Management).
Similarly for the Confluence editor, it currently cannot access content from your subpages, as it is outside the current editing surface.
Expanding the surface area from which our AI editing experience can take in context for prompts is on our team's radar to improve the features. If you're available and willing, the team and I would love to learn more about your feedback for this to help inform our roadmap! Feel free to book in a time to chat using either of these meeting scheduling links: