Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Connectors] Jira connector issue type doesn't display any values from the dropdown #186227

Open
bhavyarm opened this issue Jun 13, 2024 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Actions/ConnectorsManagement Issues related to Connectors Management UX Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@bhavyarm
Copy link
Contributor

Kibana version: main/serverless

Browser version: chrome latest

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): from QA

Describe the bug: While trying to test Jira connector, I added one along with correct url, project type, email, api but cannot test it because issue type displays nothing in the drop down on the test panel. The panel also doesn't let me know that type is missing. Instead it says "Save your changes before testing the connector." without telling me whats wrong.

issue_type_doesn.t_have.mp4
Screenshot 2024-06-13 at 6 52 04 PM
@bhavyarm bhavyarm added bug Fixes for quality problems that affect the customer experience Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Actions/ConnectorsManagement Issues related to Connectors Management UX labels Jun 13, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@bhavyarm
Copy link
Contributor Author

Zoomed with @cnasikas and we found out that its a chrome auto-fill problem. Can we disable auto-fill in connectors? Thanks Christos!

@cnasikas
Copy link
Member

cnasikas commented Jun 18, 2024

We could use the autocomplete="off" for the input fields. If this will not work we could use the autocomplete="new-text" for the username and the autocomplete="new-password" for the password in the connectors' forms. Thanks @bhavyarm for the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Actions/ConnectorsManagement Issues related to Connectors Management UX Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

3 participants