Jira
Email to Jira,
the easy way
ForwardThis is the simple tool that connects your email to Jira. Forward any email along with some simple instructions, and it’s handled. Nothing to download, nothing to set up. Works with dozens of your other apps too.
Setup in 30 seconds.
How it works
Connect Jira
Create a free account and connect Jira. It takes about 30 seconds, and you only do it once.
Forward an email
Forward any email to your ForwardThis address along with your instructions. One email can ask for several things at once.
Done.
ForwardThis replies when it's done, with a short summary and links to what it made - and an undo button if something doesn't look right.
Just forward it
to do@forwardthis.io
Fwd: Checkout failing on Safari
Raise this in the WEB project as a high priority bug, put Dan on it, and link it to WEB-290.
---------- Forwarded message ----------
Hi - three customers this morning couldn't get past the payment step on Safari. It works fine in Chrome. Can someone look at it today?
Created WEB-318
Checkout fails on Safari at the payment step · High · Dan Mercer
Linked to WEB-290
Safari payment sheet regression
Undo available for 24 hours if something does not look right.
Some other examples
- “Comment on PROJ-412 with what the client just said.”
- “Move WEB-318 to In Review and log 2h against it.”
- “Attach this spec to DES-77 and add Priya as a watcher.”
Everything ForwardThis can do in Jira
Create task
Create an issue
Update task
Transition, assign or edit an issue
Move task
Move an issue into a sprint or back to the backlog
Change tags
Change an issue's labels
Delete task
Delete an issue
Add note
Comment on an issue
Attach file
Attach a file to an issue
Link records
Link two issues
Add follower
Add a watcher to an issue
Add CRM record
Log work on an issue
Look up tasks
Look up issues
Read a record
Read an issue in full
Look up records
Look up boards, sprints and projects
Try it with a real email.
Forward any work email to the address below and see what ForwardThis can do. No signup required.
Occasional product emails may follow.
Why you need ForwardThis
Email is messy, every message asking for something different. It means constantly leaving your inbox and juggling tabs. ForwardThis skips all of that: forward an email along with some simple instructions, and it’s handled. Compatible with every email provider, and it works across the apps you’re already using.
Questions
- How do I send an email to Jira?
- Forward the email to your ForwardThis address with a line saying what you want, like "raise this in the WEB project as a bug". ForwardThis creates the issue, fills in the summary and description from the email, and replies to confirm with a link and the new issue key. The first time, you'll need a free account with Jira connected, which takes about 30 seconds - that's the entire Jira email integration.
- Can I forward an email straight into a Jira issue?
- Yes. Forward it to your ForwardThis address and name the project - "put this in WEB". You can set the issue type, the assignee, the priority and a due date in the same line, and naming a parent issue makes it a sub-task instead. If the project name could mean two things, it asks you which rather than guessing.
- Can it update an issue I already have?
- Yes. Name the issue by its key, like PROJ-123, or by its exact summary. From there it can comment, reassign, retitle, set a priority or a due date, change labels, attach a file from the email, add a watcher, log time against it, or move it to any status your project actually uses, like In Review.
- What if it raises the issue in the wrong project?
- The confirmation email includes an undo that works for 24 hours. You can also just reply - "move it to the SUP project" - and it fixes its own work.
- How is this different from Jira's own email handling or Zapier?
- Jira Service Management gives a queue its own address, so every email that arrives becomes the same kind of ticket in the same place. Zapier can do more, but you build a rule for each case first. ForwardThis uses one address for everything and reads the line you write, so this email becomes a high priority bug in WEB and the next one becomes a comment on PROJ-412. If every email you get really does belong in one queue as one ticket type, Jira's own address is simpler and free.