Jira Assistant Issues

View #319 on GitHub to know more details

#319 - "Add worklog" dialog: Field "Ticket no" looses focus on manual ticket selection

trashcandrummer commented on Aug 28, 2023

Checklist before you being

  • I am sure that I am already using latest version of Jira Assistant
  • I had verified that, no similar issues are already reported in issue tracker
  • I had tried reproducing this issue with with Web version of Jira Assistant to ensure that this issue is not recently fixed and yet to be published
  • I had verified that, my query is not answered in FAQ section of website
  • I had verified that, my issue is not listed as known bugs in website

How do you use Jira Assistant?

Browser extension

Are you using cloud version of Jira or self hosted (data center / server) of Jira.

Self hosted (datacenter)

Version of Jira Assistant


What browser are you using?


What OS are you using? You need not disclose this if you feel it is irr-relevant for your issue.


Bug Description

The focus on the field "Ticket no" (Worklog dialog) is lost when selecting a ticket from the suggestion list. This is not the case if the ticket number is inserted and e.g. auto completed by hitting TAB to move to the next field.

Working case

Ticket number was inserted and TAB was used to trigger "autocomplete"/"autoselect". The focus is now on the next field ("Work description") which is correct. JA_auto_complete

Wrong case

Ticket number was inserted (party or full does not matter) and the wanted ticket was selected by e.g. mouse click from the suggestion list. The focus is lost / set to the complete dialog instead of remaining on the "Ticket no" field to continue with e.g. TAB to jump to the next field. This is wrong and also annoying as you now have to hit TAB many times to get to the "Work description" field again. JA_manual_selection

Would be nice if this focus handling could be improved.

Checklist before you submit

  • I have ensured not to paste any confidential information like Jira url, Mail id, etc.
  • I have verified my browser console logs and added necessary details (if required)
  • I have added required screenshots if the bug is related to UI (as necessary)