Report a Bug or Request a Feature
If something is not working as expected, or if you have an idea that would make Premeena better for your school, we want to hear from you. This page explains what to include and how to reach us.
Reporting a bug
Section titled “Reporting a bug”A good bug report helps us reproduce the problem quickly and get a fix to you faster.
What to include
Section titled “What to include”| Field | What to write | Example |
|---|---|---|
| Summary | One sentence describing what went wrong | Fee receipt does not download when I click the button |
| Steps to reproduce | Numbered steps that reliably trigger the issue | 1. Go to Finance → Fees. 2. Open a student record. 3. Click Download Receipt. |
| Expected result | What you expected to happen | A PDF should download |
| Actual result | What actually happened (error message, blank screen, etc.) | A spinner appears and nothing downloads; no error is shown |
| Frequency | Does it happen every time or only sometimes? | Every time for one specific student; works for others |
| Screenshots or recording | Attach a screenshot or short screen recording if possible | — |
| Browser and device | Browser name and version, and whether you are on desktop or mobile | Chrome 124, Windows 11 desktop |
How to submit
Section titled “How to submit”Use the built-in Bug Report tool — it is available directly inside Premeena so you do not need to leave the app.
- Click your profile picture or initials in the top-right corner of any page to open the user menu.
- Select Report a Bug from the dropdown.
- Fill in the form using the fields described above and click Submit.
You can also open the bug report form directly at sma.premeena.com/report-bug.
We aim to acknowledge bug reports within 1 business day and will follow up by email as we investigate.
Requesting a feature
Section titled “Requesting a feature”Feature requests help shape the Premeena roadmap. The more context you provide, the better we can evaluate and prioritise your idea.
What to include
Section titled “What to include”| Field | What to write | Example |
|---|---|---|
| Problem statement | Describe the problem you are trying to solve, not the solution | I have no way to bulk-print all student ID cards at once |
| Who is affected | Which role or team would use this feature | School administrators at the start of each academic year |
| Proposed solution (optional) | Describe how you imagine it working, if you have a clear idea | A “Print All ID Cards” button on the Students list page that generates a single PDF |
| Workaround (optional) | How you currently handle this, if at all | We print each card individually — around 400 clicks per year group |
| Priority | How much does this block or slow down your daily work? | High — we spend 3–4 hours on this every term |
How to submit
Section titled “How to submit”Send your feature request to support@premeena.com with the subject line:
[Feature Request] <brief title>
For example: [Feature Request] Bulk print student ID cards
We review all feature requests and will reply to confirm receipt. Requests that align with the roadmap are added to our planning queue; we will reach out for any follow-up questions.
What happens after you submit
Section titled “What happens after you submit”-
Acknowledgement
Section titled “Acknowledgement”We reply to confirm we received your report or request, usually within 1 business day.
-
Triage
Section titled “Triage”For bugs, we reproduce and assess the severity. For feature requests, we evaluate fit with the roadmap and how many schools would benefit.
-
Updates
Section titled “Updates”We keep you informed by email as the issue is investigated or as the feature progresses through planning and development.
-
Resolution
Section titled “Resolution”Bug fixes are released in our regular deployment cycle. You will receive an email when the fix is live. Feature releases are announced in the platform.
Tips for faster resolution
Section titled “Tips for faster resolution”- One issue per email — separate reports are easier to track and prioritise than a combined list.
- Reply to the same thread — if you have follow-up information, reply to the acknowledgement email so everything stays in one place.
- Include your school name — this helps us look up your account and narrow down environment-specific issues quickly.