Bug Jira connection: sometimes, the Jira connection is lost, requiring a restart of the Client

I successfully connected one of my repos/workspaces to Jira. In the mouse-over tooltip I see the ticket name, and can click the link to the ticket:



However, several times now this connection is simply lost. The branch explorer view reverts to a view as if the project was not connected (=the ticket link is missing, and the branch name does no longer show the ticket title as subtext, just the prefix_XYZ). I have to explicitly close and restart the client to re-activate the connection:



So far I was unable to determine under which circumstances this happens, or whether it happens sporadically or constantly. It possibly happened after committing some changes, and/or switching branches.

Additional info: we use Jira Cloud in a company-managed project (=a "next-gen" project). We have the custom field "Plastic SCM" created, but as it is a "next-gen" project, it is not used at all, and the auto-commenting in fact only succeeds if that Custom ID is empty in the Plastic configuration. However, as the Jira comment posted for every commit is quite "spammy"/verbose, and contains little useful info, it is possible the problem occurred after committing a change while the Custom ID field in the Plastic configuration contained a number (valid or not), which is currently our workaround to PREVENT Plastic from adding these Jira comments...

-----

Additional feature idea: make the amount of info posted as Jira comments configurable. Rarely, you'll want a 10-100 line detailed info with all headers - this can become quite messy for large feature branches - especially if you use the Jira comments to actually DISCUSS important things. Instead, it might suffice to JUST post the changeset ID plus the commit message, IDEALLY with an actual backlink into Plastic (which the Plastic client actually supports!):

plastic://ssl://SERVER:8088/repos/REPONAME/changesets/1438/diff

 

If it happens again, I can open a support ticket with more info.
Currently we're not really using the Jira extension regularly.

 

@carlosalba1985
I was able to consistently reproduce the problem after a checkin operation, and to me it appears the problem is connected to an (intentionally) unconfigured Jira custom field.
I opened a support request, with attached logfile: https://support.unity.com/hc/requests/1614483