Convince My Boss
Move issues between projects on demand, or automatically when a rule says they belong somewhere else.
Tickets land in the wrong project constantly. A request goes to the service desk that should have gone to engineering, a bug gets raised against the wrong product, a task belongs to a different team. Moving them one at a time through Jira’s native flow is slow, and because it is slow, people leave them where they are and the reporting stops reflecting reality.
Below are two emails you can copy, adjust and send.
Informal Email
Subject: Something to stop tickets sitting in the wrong project
Hi [Recipient’s Name],
Hope you’re well.
We lose a surprising amount of time to tickets being raised in the wrong project. Moving them individually is tedious enough that people mostly do not bother, so our project reporting is not really accurate.
There is an app called Move It from Redmoon Software that handles this:
- Move issues without the manual grind. Straightforward moves between projects rather than clicking through the native flow one ticket at a time.
- Automate the routine ones. Where the routing is predictable, a rule can move the issue automatically so nobody has to triage it by hand.
- Reporting becomes trustworthy again. If tickets sit in the right project, per-project metrics actually mean something.
More here: Move It.
Worth a trial. Most of the benefit is time we currently spend on triage.
Best,
[Your Name]
Formal Email
Subject: Recommendation to adopt Move It to reduce manual triage effort in Jira
I hope this message finds you well.
I am writing to recommend Move It from Redmoon Software to reduce the administrative overhead of routing Jira issues to the correct project.
A consistent proportion of incoming issues are raised against the wrong project, whether through a service desk request that belongs with a delivery team, a defect logged against the wrong component, or work that transfers between teams. Native Jira supports moving issues, but the process is manual and per-issue. The practical consequence is that many issues are simply left in place, which degrades the accuracy of project-level reporting and capacity planning.
Move It addresses this:
- Reduced manual effort. Moving issues between projects becomes a routine action rather than a task people avoid.
- Rule-based automation. Where routing follows a predictable pattern, issues can be moved automatically, removing the triage step entirely for those cases.
- Improved reporting integrity. Project metrics, throughput and capacity figures only hold if issues sit in the correct project.
- Low change impact. This affects administration of issues rather than how teams work day to day.
Further detail: Move It.
For a security review, the app is Cloud only and is built Forge-native, so data remains inside our own Atlassian Cloud site. Our Cloud Security Statement and Data Processing Agreement cover it.
The business case here is straightforward time recovery, so a trial across our highest-volume intake project should make the value clear quickly.
Best regards,
[Your Name]