OJS Feature Request Template
Use this to submit new features, enhancements, or bugs that impact users.
1️⃣ Feature Summary
A short, clear title that describes the request.
→ Example: “Bulk assign reviewers to multiple submissions.”
2️⃣ Request Origin
Where and how was the need identified?
- Request raised by: (e.g., Journal Manager, Support Ticket, Forum Post)
- Stakeholders affected: (e.g., Editors, Reviewers, Authors, Translators)
- Region or context (optional): (e.g., multilingual journal, low-bandwidth region)
3️⃣ User Problem (not the solution)
Describe the problem from the user’s point of view.
→ Example: “Editors need to assign the same reviewers repeatedly, which leads to repetitive clicking and errors.”
4️⃣ Why This Matters
Explain the real-world impact.
- Does it block core tasks or cause errors?
- Does it disproportionately affect certain users (e.g., small teams, multilingual workflows)?
- How does it relate to our strategic goals (e.g., accessibility, scalability)?
5️⃣ Current Workarounds
Are users using spreadsheets, external tools, or manual hacks to get around this?
6️⃣ User Scenarios
Provide 1–2 short stories that illustrate how this problem plays out.
→ “As an editor handling 30 submissions, I want to assign the same 4 reviewers without doing 120 manual actions.”
7️⃣ Supporting Evidence
Quotes, support tickets, UX insights, screenshots, forum threads, error logs.
→ “We spend hours re-assigning reviewers for each new submission.”
8️⃣ Priority Assessment
Helps triage the request:
| Factor |
Description |
| Impact |
High / Medium / Low |
| Reach |
Many users / One team |
| Effort |
Low / Medium / High |
| Urgency |
Blocking / Repeated ask / Nice to have |
✅ Final Checklist
- Clear user problem
- Real-world scenarios
- Supporting evidence
- Self-assessed priority
- Related links or tickets
OJS Feature Request Template
Use this to submit new features, enhancements, or bugs that impact users.
A short, clear title that describes the request.
→ Example: “Bulk assign reviewers to multiple submissions.”
2️⃣ Request Origin
Where and how was the need identified?
Describe the problem from the user’s point of view.
→ Example: “Editors need to assign the same reviewers repeatedly, which leads to repetitive clicking and errors.”
4️⃣ Why This Matters
Explain the real-world impact.
Are users using spreadsheets, external tools, or manual hacks to get around this?
6️⃣ User Scenarios
Provide 1–2 short stories that illustrate how this problem plays out.
→ “As an editor handling 30 submissions, I want to assign the same 4 reviewers without doing 120 manual actions.”
7️⃣ Supporting Evidence
Quotes, support tickets, UX insights, screenshots, forum threads, error logs.
→ “We spend hours re-assigning reviewers for each new submission.”
8️⃣ Priority Assessment
Helps triage the request: