rmtrack.com Paid content Trial available

What is RMTrack?

RMTrack is a web-based issue, bug and defect tracking application from RMTrack. It is aimed at teams that need to log, assign, filter and report on work items, and it also covers help desk and quality assurance use cases. It is downloadable and offered with a free 14-day trial.

What it does

• Issue lists and filtering: The main page shows items the logged-in user can access. Lists can be filtered by clicking conditions, sorted on multiple columns, and columns rearranged by dragging. Filters and column layouts can be saved and shared.
• Exports: A list can be downloaded as .xlsx or .csv in one click.
• Reporting: A custom reporting engine supports dashboard, columnar, chart (bar, line, pie) and HTML-template-driven reports. Column-oriented reports can include drilldown hyperlinks.
• Custom forms and fields: Each project can have its own data entry form or share a common one, and public forms can be defined for anyone to submit information. Field types include text, numeric, dropdowns, dates, checkboxes, computed fields and logged comments. Dropdowns can be multi-level.
• Permissions and audit: Group-level security controls field permissions (none, inquiry, update), and there is an audit trail of all changes.
• Notifications: Email notification rules are customizable per project or shared across projects, with recipients by function such as creator or assignee.

Who it suits

A small software team that wants a configurable tracker without building one from scratch is the clearest fit: define a project form, add custom fields, set notification rules, and use saved filters for daily triage. A manufacturing or business-process team may also fit, because the page notes support for a wide range of business and manufacturing processes and offers help configuring it. A public-facing help desk is plausible too, given public submission forms and email notifications.

Trade-offs to weigh

The feature list is broad but traditional: forms, fields, filters, reports and email. If your team expects a modern chat-like interface, built-in automation or deep code-repository integration, that is not what the page describes. Customization is a strength, but it also means someone must decide on forms, fields, dropdowns and permissions before the tool becomes useful. Reporting looks strongest for structured, column-based views; the HTML template option gives flexibility at the cost of more setup work.

Next step

Start the free trial and test it against one real workflow: create a project, add the fields you actually use, set one notification rule, and build a saved filter your team would check each morning. If that takes more configuration than you are willing to maintain, the tool is probably too heavy for your needs. If it fits, use the same setup as the basis for a second project to see how well shared forms and rules scale.

How does RMTrack's 14-day free trial work and what are the limitations?

RMTrack's free trial is a 14-day evaluation of its web-based issue tracking software, and the page states it requires no credit card. You get the full application for that period rather than a stripped-down demo, so you can test whether its form designer, filtering and reporting fit your process before committing.

What the trial gives you

• Access to the same core features the paid product advertises: customizable data entry forms, custom fields, dynamic filtering, .xlsx/.csv list exports, and the custom reporting engine with dashboard, columnar, chart and HTML-template report styles.
• Support during evaluation. The site explicitly invites evaluators to call or email the support group with configuration questions, which is unusual and useful if your workflow is non-standard (the page mentions business and manufacturing processes).
• A downloadable option alongside the hosted web application, so you can judge deployment fit.

Limitations to plan around

The page does not publish trial-specific caps, such as a user limit, project limit, or feature gating. Treat any such limit as unknown and confirm it with support before you build an evaluation plan around it. The real constraint is time: 14 days is short for a team rollout, so decide in advance what you need to prove.

A practical way to use the 14 days

1. Days 1–2: configure one project's form and custom fields to mirror your actual intake data.
2. Days 3–5: have two or three colleagues file and update real issues, including attachments and comments.
3. Days 6–8: build the reports your manager actually asks for and test the drill-down links on columnar reports.
4. Days 9–11: test email notification rules, including whether per-project rules or shared rules suit your teams.
5. Days 12–14: export lists, review the audit trail, and compare against one alternative.

Choosing between this and alternatives

If your priority is heavily customized forms, multi-level dropdowns, field-level permissions and flexible reporting, RMTrack is aimed squarely at that. If you want a lightweight tracker your team can adopt without configuration, a simpler tool may cost less effort. For a well-known hosted alternative, see Atlassian (Jira); for open-source self-hosting, Bugzilla or MantisBT are established options. Compare on setup effort, reporting flexibility and how your non-technical staff find the data entry forms.

Before the trial ends, ask RMTrack support directly about user limits, data retention after expiry, and whether your trial configuration can be carried into a paid account.

How can I customize RMTrack's data entry forms and custom fields for my team's workflow?

RMTrack lets you shape each project’s data entry form and field set around your team’s actual process, rather than forcing everyone into one generic issue form. The main levers are the form designer, per-project form assignment, public forms, multi-level dropdowns, field types, and field-level security.

How the customization pieces fit together

• Form designer: Build data entry forms with a drag-and-drop designer. This is where you decide which fields appear, in what order, and how the form is laid out.
• Per-project forms: Each project can have its own form, or projects can share a common form. Use separate forms when workflows differ meaningfully; share one when you want consistent intake across teams.
• Public forms: Define forms that anyone can use to submit information. This is useful for help desk intake or outside contributors who should not see the full internal tracker.
• Custom fields: Available field types include text, numeric, dropdowns, dates, checkboxes, computed fields, and logged comments. Computed fields can derive values automatically, while logged comments capture discussion alongside structured data.
• Multi-level dropdowns: Dropdown lists are fully customizable and can be multi-level, which helps when one choice should narrow the next set of options.
• Field-level security: Group-level permissions control what each user group can do with a field: none, inquiry, or update. This is how you keep sensitive fields visible to some groups and hidden from others.
• Attachments and audit trail: Forms support drag-and-drop file attachments, and changes are tracked in an audit trail.

A practical way to map your workflow

1. List your stages and decisions. Write down how an issue moves from report to resolution and what information is needed at each stage.
2. Separate universal fields from project-specific ones. Put fields every project needs on a shared form; give projects with special needs their own form.
3. Choose field types deliberately. Use dropdowns for controlled vocabularies, dates for deadlines, checkboxes for binary flags, computed fields for values you would otherwise calculate by hand, and logged comments for context that does not fit a fixed field.
4. Use multi-level dropdowns for dependent choices. For example, a category selection can drive a narrower subcategory list.
5. Set group permissions per field. Decide which groups get none, inquiry, or update access, especially for cost, customer, or internal-only fields.
6. Add a public form where outside submission makes sense. Keep it narrow so external submitters provide only what you need to triage.
7. Test with a real workflow. Run a few representative issues through the form before rolling it out, then adjust field order and required fields.

Trade-offs to weigh

• One shared form vs. per-project forms: A shared form is simpler to maintain and gives you comparable data across projects. Per-project forms fit distinct workflows but multiply the number of forms you must keep aligned.
• More fields vs. faster entry: Every added field slows down the person submitting the issue. Computed fields and multi-level dropdowns can reduce manual entry, but they still need setup and maintenance.
• Strict field security vs. collaboration: Restricting a field to inquiry or none protects sensitive data, but it can also hide context that would help someone resolve the issue.
• Public forms vs. data quality: Public forms widen the funnel, but you may need extra triage rules to clean up submissions.

If you are evaluating RMTrack, the fastest next step is to sketch one real workflow on paper, then build a single project form that matches it and test it with two or three actual issues. For broader context on how this category of tool is positioned, see RMTrack.

What reporting and dashboard options does RMTrack offer for tracking issues?

RMTrack's reporting is built around a custom reporting engine rather than a fixed set of canned reports. According to the product's own feature description, you can choose among several report styles: dashboard views, columnar reports, charts (bar, line and pie), and an HTML template-driven report for cases where you need full layout control. Column-oriented reports support drilldown through hyperlinks, so a summary figure can be clicked to reach the underlying issues.

Where the dashboard fits

The dashboard is one presentation style within that reporting engine, not a separate analytics module. Practically, that means a manager who wants an at-a-glance status view and an analyst who wants a detailed tabular export are working from the same reporting tool, choosing different output formats.

Filtering feeds the reports

Reporting sits on top of the main issue list, which drives much of the day-to-day tracking:

• The main page lists only items the logged-on user can access.
• Lists can be filtered by clicking conditions rather than building queries.
• Sorting works across multiple columns, and columns can be rearranged by dragging.
• Filters and column layouts can be saved and shared between users.
• Any list can be exported to .xlsx or .csv in one click.

That last point matters: for many teams, the fastest "report" is a filtered list exported to a spreadsheet, with the reporting engine reserved for recurring or presentational needs.

Custom fields and forms shape what you can report on

Custom fields include text, numeric, dropdowns, dates, checkboxes, computed fields and logged comments, and forms can be defined per project or shared. Field-level permissions are set at none, inquiry or update. Because reporting draws on these fields, the quality of your reports depends on how deliberately you design forms and fields up front — a computed field or a multi-level dropdown added later will not retroactively populate historical issues.

A concrete scenario

A support lead at a small manufacturing firm could create one form for customer-reported defects and another for internal QA findings, then run a columnar report grouped by product line with drilldown to individual tickets, and share a saved filter with the on-call engineer. A weekly pie chart of open issues by assignee would come from the same engine.

Choosing between the options

Next step

Before committing, list the three reports your team actually reviews each week, then check whether each maps to a dashboard, columnar or chart style — and confirm the custom fields those reports depend on already exist in your form design. RMTrack offers a 14-day free trial without a credit card, and its support group explicitly invites evaluation calls about configuring the product for specific business and manufacturing processes, which is the right moment to ask how your reporting requirements would be set up. See RMTrack for details.

How does RMTrack handle email notifications and user permissions?

RMTrack treats email notifications and user permissions as separate, configurable systems that both tie back to projects. Notifications are rule-driven and project-scoped; permissions are role-based and can be enforced down to the individual field.

Email notifications

RMTrack uses customizable notification rules to keep project members informed about assignments. Each project can define its own rules or inherit shared rules that apply across all projects, so you can standardize alerts for some teams while letting others tune them. Recipients can be targeted by function — for example, the creator or the assignee — rather than naming individuals every time.

A practical scenario: a QA lead wants the assignee notified on every new defect, but the project manager only on priority-one items. With project-level rules, the QA project can carry the broad rule while a shared rule handles the escalation. The trade-off is administrative: the more project-specific rules you create, the more places you must update when staff or processes change.

User permissions

The page evidence describes two permission layers:

• Group-level security controls what each user group can do with individual custom fields — none, inquiry, or update.
• Customizable forms determine what data entry looks like, and forms can be per-project or shared. Public forms let anyone submit information without a full account.

Because field permissions are group-based, you can show a computed field to managers while hiding it from submitters, or let a support group read a field but not change it. This is useful when external or junior users share the same form as internal staff.

How the two interact

Notifications follow the work; permissions constrain who can see or change it. A user who lacks update rights on a field can still receive an email about a change to that field, depending on how the rule is written. If your process depends on strict information barriers, review both settings together rather than assuming notifications respect field-level visibility.

Next step

If you are evaluating RMTrack, list the roles in your team and the fields each role should read or edit, then map those to groups. Separately, write down which events should trigger email and who by function should receive them. The support group is explicitly offered for help configuring RMTrack to specific business and manufacturing processes, and the Administration and User Guide covers the mechanics. You can also compare against other trackers — for example, Bugzilla for open-source defect tracking or Atlassian for Jira's permission schemes — to see whether RMTrack's project-level rule model fits your governance needs.

What are the pricing plans for RMTrack and how do I purchase it?

RMTrack does not publish its pricing plans on the page described here. The site shows a Pricing page and a Buy page, plus a free 14-day trial with no credit card required, but the plan names, tiers, seat counts and prices are not stated in the available information.

What you can do now

• Start the free trial to evaluate RMTrack before committing to a purchase.
• Open RMTrack's Pricing page to see current plans and terms.
• Use the Buy page when you are ready to purchase.
• If your needs are unusual, contact RMTrack support during the trial. The site explicitly invites evaluation questions about configuring RMTrack for specific business and manufacturing processes.

How to choose a plan once you see the options

Practical example

A 12-person QA and support team evaluating RMTrack would typically run the 14-day trial with a small pilot group, configure one project's custom form and fields, test a saved filter shared between users, and export a list to .xlsx. That gives a realistic sense of fit before you compare plan costs per user.

Decision criterion

If your main need is lightweight issue logging, a lower-cost tier may be enough. If you need custom forms per project, field-level permissions, multi-level dropdowns and the custom reporting engine, expect to pay for a higher tier or a configured setup. Confirm the current pricing and purchase process directly on RMTrack's Pricing and Buy pages, since those details are not available here.