Skip to content

Conversation

@teresaromero
Copy link
Contributor

What does this PR do?

Adds a new issue template to file categories propsal.

Why is it important?

In order to discuss the change and follow the implementation plan

Checklist

Related issues

Related #430

@teresaromero teresaromero requested a review from a team as a code owner December 2, 2025 12:06
@teresaromero teresaromero marked this pull request as draft December 2, 2025 13:53
…eligibility requirements and proposal process
@teresaromero teresaromero marked this pull request as ready for review December 2, 2025 15:40
Copy link
Member

@jsoriano jsoriano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. @nimarezainia could you please also take a look?

- Enhancement requests that complain about the lack of this category.
- Full-story data reporting on average 50+ unique searches for this keyword per month in the integrations UI.
- Usage of this category for filtering purposes by our industry.
- [ ] Impact that are we expecting with this category and how we will measure it (success criteria)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about possible answers to this point. @nimarezainia are we checking some telemetry related to categories?

@jsoriano jsoriano requested a review from nimarezainia December 2, 2025 17:25
Co-authored-by: Jaime Soriano Pastor <[email protected]>
@elasticmachine
Copy link

💚 Build Succeeded

History

Comment on lines +41 to +45
3. Ecosystem team assesses the request and makes a decision based on data points provided in the GitHub issue
4. If we are not able to address and the category doesn’t meet eligibility requirements, we can assume that
this category is more harmful to the UX than the value it provides, and hence, it must not be added.
5. If the decision is in favor of adding the category, the Ecosystem team will prioritize and work on the GitHub issue in
one of the releases under planning (future releases)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to this , should this issue be added the Team:Ecosystem label directly when it is created ? Or should it be added by the user once it has all the data ? @kpollich

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants