Submitting incubator tickets
At Magnolia, our Incubator team works on modules in structured development batches. To help us work more efficiently and increase the chances of your ticket being picked up sooner, we encourage you to follow the guidelines below when submitting an Incubator ticket.
What to include in your ticket
Description
Start with a clear and detailed description of your issue, request, or improvement idea. The more context you can provide, the better.
Use Case
What are you trying to achieve? Describe the scenario where this ticket comes into play. A strong use case helps us understand the practical value and priority of your request.
Proposal (optional)
If you’ve already thought of a possible solution or even implemented a hotfix, feel free to share it.
You can:
-
Describe the approach or logic
-
Share code snippets or configuration ideas
-
Link to a public repo or reference implementation
Impact
Tell us how this affects you. Consider both the positive impact if fixed and the negative impact if left unresolved.
For example:
-
Improved developer experience
-
Reduced complexity
-
Increased security
-
Broken UI, performance issues, or blocked users
Steps to reproduce or validate
Give us a detailed, step-by-step guide:
-
How can we reproduce the issue or verify your suggestion?
-
Include YAML configs, paths, and precise steps.
-
Screenshots, logs, or screen recordings are highly appreciated.
-
Write this section as if we’re not part of your project. This ensures clarity for everyone involved.
Template for Jira
Copy the template below when submitting a ticket in Jira.
h2. Description
Provide a clear and detailed description of your issue, request, or improvement idea
h2. Use Case
What are you trying to achieve? Describe the scenario where this comes into play
h2. Proposal (optional)
If you have a possible solution or approach in mind, share it here
h2. Impact
How does this affect you? Consider both positive impact if fixed and negative impact if unresolved
h2. Steps to reproduce or validate
Provide detailed, step-by-step instructions. Include configs, paths, screenshots, and logs if applicable
h2. Expected vs current behavior
*Expected:* What behavior did you expect?
*Current:* What is the current behavior instead? Any errors or log messages?Intellectual property note
By submitting proposals, configuration snippets, or code examples as part of your ticket, you agree that Magnolia may use, adapt, and incorporate your contribution into its products or services without obligation to attribute or compensate you. You confirm that you have the right to share this material and that it does not infringe on any third-party rights.