Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Google docs selection not working for Insights

If I try to create an insight from Google Docs using the Chrome plugin, it doesn't work - the message "Text selection is not working in Google Docs now" is displayed.

I understand there's a technical problem, but I've been trying to find more information about it, without success. Is there any good workaround (other then doing a screenshot instead)? Are there any expectations on when this might be solved?


2 answers

2 accepted

Suggest an answer

Log in or Sign up to answer
0 votes
Answer accepted
Hermance NDounga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 27, 2023

Hey Milan, 

it was previously working and due to a change on Google Doc side, we are now unable to integrate with it :/ that's why this text is displayed. 

We are planning to find another way here, but it's going to be an important effort, so for the moment the workaround would indeed be to copy over in Confluence. 

It's good to know that it may not be so fast, so it makes sense to invest time into the workaround. Thanks for the update @Hermance NDounga!

0 votes
Answer accepted

@Milan Andjelkovic while not an efficient workaround, I uploaded the google docs to Confluence and captured insights from the Confluence page

Yes, that occured to me also while writing the question :) not ideal, but a possible workaround, thanks

AUG Leaders

Atlassian Community Events