How can I keep Rovo from getting in the way when I try and paste data?

[Steve Brecheisen]

I frequently paste data into Jira for our work items and that used to work great.  But now a lot of time when I go to paste data into comments or other fields it just reacts and goes to the top of the screen rather than just pasting the data.  This makes Jira much less useful for debugging issues, to get real details I have put everything in as an attachment which is time consuming or simply not include the details.

[Jean Horn]

Hi @Steve Brecheisen !

I completely feel your pain, this is definitely one of those daily annoyances that can throw off your entire workflow when you're in the middle of debugging.

This is actually a known issue that Atlassian is currently tracking across a few open bug tickets, but unfortunately, there isn't a permanent fix rolled out just yet.

In the meantime, the most reliable workaround is:

1. Click back into the field (or click away and re-focus on the comment box) right before pasting.
2. If that still acts up, try pasting using Ctrl + Shift + V (or Cmd + Shift + V on Mac) to insert plain text, which often prevents the auto-scroll glitch.

It’s definitely not ideal, but hopefully, the Atlassian team resolves the underlying bug soon!

Some related issues

• JRACLOUD-82937 Jira switching focus while typing in various fields
• JSDCLOUD-13522 Typing in a Paragraph form field, sometimes the field is out of focus, Jira window auto scrolls and the user ends up typing in a random field 

Hope this helps!

[Steve Brecheisen]

Thank you for the reply.  Unfortunately I tried both (1) and (2) and neither seemed to make a difference, at least with the data I was trying to paste when I submitted this.  I had previously seen (1) on the forum and it seems there have been times where that maybe helped, but unfortunately neither seem to help with at least pasting a few lines like the example below which I can't paste into a comment.

It works if it's a "normal" PLACEHOLDER1 situation, (1) and (3) below, but not if it's a PLACEHOLDER2 situation it goes into the non PLACEHOLDER3 and ends up being shown as PLACEHOLDER4.

(1) Aug 14 07:19:06 PLACEHOLDER5: Warning:PLACEHOLDER6.cpp:534: PLACEHOLDER7: PLACEHOLDER1
(2) Aug 14 09:28:05 PLACEHOLDER5: Warning:PLACEHOLDER6.cpp:534: PLACEHOLDER7: PLACEHOLDER2
(3) Aug 14 10:57:00 PLACEHOLDER5: Warning:PLACEHOLDER6.cpp:534: PLACEHOLDER7: PLACEHOLDER1