![]() ![]() ![]() This leads to situations, where emails pile up in this folder, often unread and unnoticed. Team members often filter these email notifications using an Outlook rule, which moves them to a “Jira” folder in their inbox. Best practice #3: use Outlook rules to organize Jira emailsĪs mentioned in the previous tip, receiving a lot of emails from Jira Software is commonplace. If you feel they are adding noise more than they are helping though, talk about saner notification settings with your friendly neighborhood project administrator. In many cases, it makes sense to be informed about these kinds of changes. For example, email notifications can be turned off for certain events like: Your project administrator can configure the notifications to be very fine-grained and to fit the needs of your team. When participating in such high volume projects, it’s easy to lose the overview, especially if you are receiving other emails as well.īut don’t take these emails as a given. ![]() Jira Software can send a lot emails if there are a lot of active projects with lots of issues. Neat, huh? Best practice #2: tune down Jira email notifications You can also specify a default importance setting, which will be used to set the priority of the new issue in Jira.Ĭommenting on existing issues works pretty much the same as creating issues. Just prepend the issue key to the subject. Jira will take care of finding the correct issue and add the email text as a new comment. Give your new quick step a catchy name and enter the Jira email address. Make sure to keep the “subject” part. To do this, click Create New in the Outlook quick steps area. Pro tip: Make sure to remove all unnecessary text from the subject and the email body, like the “FW:”-prefix.Īnd to create issues even quicker, you can create a new quick step in Outlook. For example, using the following subject line will create a new issue called “Link to Help Pages do not work” in the project that is configured for this mail handler. To do this, you can forward your customer email your Jira email address. The subject will be used to determine the title of the issue. A customer sends a bug report and you need to enter this into Jira Software to make sure it’s tracked and prioritized by your development team. ![]() You just need to know the following basics to get started.Ĭreating a new issue is probably the most common use case for integrating Jira Software and Outlook. The mail handler needs to be configured by a Jira administrator and, once set up, it will work for every product. For cloud systems, the default is: mysystem. Using this is as simple as sending an email to the address of your Jira system. (Note: I’ll be talking mostly about Jira Software, but these tips apply to Jira Core and Jira Service Desk as well.) Best practice #1: create Jira issues via emailĭid you know that Jira Software already offers an email integration out-of-the-box? It’s called the “incoming mail hander” and can be used to create new issues or add comments to existing issues. Have you ever wondered “Is there is a faster way to create a new issue?” Or “How do I work with the Jira Software notification emails?” These four best practices will answer those questions and show you how to get the most out of using Jira Software and Outlook together. In a software development setting, it’s a common requirement to transfer information from emails to Jira Software, Jira Core, or Jira Service Desk. And when we are talking email, Microsoft Outlook is the go-to tool. In most organizations, email is still the preferred medium for communication. This is a guest post by Tobias Viehweger, cofounder at yasoon, creating awesome Outlook apps for everyone. ![]()
0 Comments
Leave a Reply. |