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

Append processor adds blank value by default #75509

Closed
lockewritesdocs opened this issue Aug 19, 2020 · 5 comments
Closed

Append processor adds blank value by default #75509

lockewritesdocs opened this issue Aug 19, 2020 · 5 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Ingest Node Pipelines Ingest node pipelines management Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@lockewritesdocs
Copy link

Kibana version:
8.0.0 (SNAPSHOT)

Elasticsearch version:
8.0.0 (SNAPSHOT)

Server OS version:
macOS Catalina 10.15.6 (19G2021)

Browser version:
Chrome 84.0.4147.125

Original install method (e.g. download page, yum, from source, etc.):
https://snapshots.elastic.co/8.0.0-d196c3d2/downloads/kibana/kibana-8.0.0-SNAPSHOT-darwin-x86_64.tar.gz

Describe the bug:
When adding an append processor, the UI adds a blank value by default. If the user does not delete that blank value, it gets added to the specified field as a value.

Steps to reproduce:

  1. Access Kibana. Go to Management > Stack Management.
  2. Choose Ingest Node Pipelines.
  3. Click Create a pipeline.
  4. Click Add a processor, and then choose Append as the processor type.

Expected behavior:
All fields are blank and require input from the user.

Screenshots (if relevant):
The blank value is visible when selecting Append as the processor.
image

If the user does not delete the blank space, it is added as a value.
image

Any additional context:
This is the first bug that I've reported. I'm pretty sure it's valid!

@TinaHeiligers TinaHeiligers added the Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more label Aug 21, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

@TinaHeiligers
Copy link
Contributor

I tried to reproduce the issue but it seems to have been fixed recently.

@cjcenizal cjcenizal added bug Fixes for quality problems that affect the customer experience Feature:Ingest Node Pipelines Ingest node pipelines management labels Aug 21, 2020
@cjcenizal
Copy link
Contributor

@alisonelizabeth Could you take a look at this please?

@alisonelizabeth
Copy link
Contributor

I'm not able to reproduce either. There have been some changes made to the form library recently, which may have resolved this (#75302). @lockewritesdocs can you retest with the latest from master and see if you're still able to reproduce?

@lockewritesdocs
Copy link
Author

@alisonelizabeth, I just pulled a build from master that was built on August 21, and the issue seems to be resolved now. Thank you for investigating! I'll mark this one as closed.

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:Ingest Node Pipelines Ingest node pipelines management Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

No branches or pull requests

5 participants