Page tree

We've heard it once and a while about how hard it was to implement a use-case like this:

Every morning at 9AM I want to notify assignee of the issue about the tasks which are due today.

So far, a typical Jirassimo-style resolution of this problem was as following:

  1. Create a new custom scheduled messenger and assign a cron rule
  2. Define JQL filter for tasks like this: project = TEST and assignee in (johndoe)
  3. Define subject, email address (from $issue.fields.assignee.emailAddress) and body of the message

If it doesn't sound like a lot to do, then consider that normally, there are dozens of users and all of them would like to receive notifications about tasks assigned to them and due today. If you were to omit assignee in (johndoe) part of the query, then, of course, you'd receive all of the issues due today, but EVERYONE in your team would receive the same list of issues in email message...

 

Obviously, this is not what you're aiming to do, so the only option you could have used so far was to create (clone) N messengers only changing the assignee in (johndoe) condition to fit a particular user. This technique was both error-prone and maintenance demanding. Just imagine a team of 200 and 200 corresponding messengers....

 

How could you force Jirassimo to send notifications in batches like this: first for userA and then for userB?

IssueAssignee
MFP-1userA
MFP-2userA
MFP-18userA
MFP-5userB
MFP-8userB

 

Good news, now you can solve it. Just tell us which field contains your user email and remove assignee in (userabc) in your JQL statement. Instead of that, you could write something like this:

project = TEST and and duedate >= now() and assignee in membersOf("YOUR_JIRA_USER_GROUP")

This will ensure that Jirassimo collects all issues which are due today and are in project TEST and are assigned to users belonging to YOUR_JIRA_USER_GROUP.

After selecting all these issues, Jirassimo will group issues by Group By field and run messaging in batches. There will be as many batches as there are different values for specified Group By.

Finally, to specify Group By, you should use the following syntax:

fields.assignee.emailAddress

This will work for assignee emails. Another options available are:

fields.reporter.emailAddress

fields.creator.emailAddress

fields.younameit.emailAddress (smile)

Enjoy!

 

 

 

What was the last time you learned a new programming language? Was it when you created a new Jirassimo messenger just staring at the empty template editor and guessing how would I do it?

What’s that Velocity syntax they’re talking about?

How do I find and access JIRA fields?

How do I specify conditions?

How's that field named. customfield_xxx ?

It might surprise you, but there’re many users who had the same concern. Even we, as developers of this addon, sometimes find it inconvenient and prefer to do a quick Google search rather than learning Velocity templates and the JSON structure of Jira issues.

Good news is that these days are finally over! We’ve made template writing as simple as drag-n-drop with your mouse (or touchpad if you prefer)! Just give as a sample JIRA issue key and we’ll show you what it has insight – all standard and custom fields in a human-friendly language (no customfield_..... anymore). Scroll to the one(s) you need and drag and drop them to the editor. The Velocity code will be auto-generated for you.

Even though template constructor saves you from manual typing of Velocity there still times when you might want to tweak it manually. And we know that it was anything but convenient before – so here you go – we have syntax highlighting and autosuggesting features. Just type dot (.) and see what fields are available in that structure. Not sure about the field name? Just type it’s human-friendly name in the search and find it out!

 

Available for cloud version of Jirassimo. If you use our PDF add-on stay tuned, it's coming soon!

Enjoy!

More and more businesses are discovering Atlassian JIRA as a robust tool to manage their business processes. What started as a toolbox for IT people, eventually emerged into a system that is gaining wide acceptance in a variety of fields outside of IT. This is primarily due to it's customizable and powerful workflow engine.

If we look at a business process from a technical point of view, then we'll see that it's nothing but a specialized workflow with its unique statuses, transitions, and rules. As JIRA provides excellent support for custom-tailored workflows, it's natural to use it to drive your processes.

One of their specialties in driving business processes is that they often incur specific documentation that has to be produced when a specified event occurs. For instance, writing meeting minutes, submitting an approved expense report after a business trip or filing an invoice are all examples of documents that have to be produced. It's often the case that all the necessary data for these documents is kept in JIRA.

Here comes the challenge - how would you convert the data from your JIRA issue into a professional-looking PDF document that you can use internally and externally? JIRA allows you to export an issue into a PDF; however, you're limited in terms of its appearance. If you need something more than a plain A4 or 8.5x11 sized-document, then you have to go for an add-on.

Our PDF Documents Exporter add-on is the first and only add-on for JIRA Cloud It allows you to export your JIRA issue as a PDF document with full control over the content and appearance. Technically, everything a JIRA issue contains can be rendered in a PDF, and it doesn't matter whether the information is kept in a standard or custom field. Your IT person will need to create and name the PDF generating template. Whenever you need a PDF from your JIRA issue, you just go to the issue detail screen, click Generate PDF, select the template, and click Generate. That simple!


How much time have you wasted looking for that email containing vital information to help you make strategic decisions on your project? Sometimes relying on the built-in notification system in JIRA or JIRA Service Desk just does not cut it. That lost time could have been better spent working on other project-related matters.

Using a custom notification solution with JIRA can alleviate some of the challenges faced when meeting the demands of your project. Make the most of your project communications, so they don’t turn out to be time wasters. Making communication clearer and more structured can minimize notification challenges. 

Here are five benefits you obtain from implementing a custom notification solution with JIRA.

Reduce the Number of JIRA Emails

The team just finished their meeting reviewing and updating the open JIRAs. Your inbox is inundated with many notifications. You start opening one right after the other to review the updates. You wonder why can’t they just be consolidated into one email. 

Or you are an IT manager. How nice would be to receive a digested summary of the changes you care about, with the granularity that you need, from all the JIRA projects on Monday morning.

Sounds familiar? The number of JIRA notifications received after a meeting can be overwhelming. Consolidating them reduces the number of emails hitting your inbox. The result is less clutter, saves you time from going through them and increases your productivity.

Set Reminders

Sometimes, there’re a few issues that you want to track because the customer has requested that they are resolved in time for the delivery of the project. You want to make sure that they are updated before the next meeting. Setting a reminder helps you to remain connected with the issue and stay on track of its progress.

Stay Informed

Changes or updates made to an issue? New tasks created? Send scheduled digest notifications daily or weekly to your inbox, Slack or HipChat channel. Stay informed and up-to-date with the latest information. Regular notifications will help you make decisions to keep your project on track.

Notify Your Customers

Sometimes customers want to be kept abreast of issues that affect them. Implementing a custom notification solution can help keep them informed and aware of the progress being made with an issue. 

Sometimes language is an issue. The implemented solution must be able to support the information in the preferred language of your customers. 

Automating notifications to customers is an efficient and effective way to manage and share information. You benefit by not having to follow up from the built-in JIRA notifications manually. This is especially important for those folks who use JIRA Service Desk.

Customize the Message

When sending communications to customers, you would like to customize what they receive. You may want to share only specific fields of a notification and insert your corporate logo, so they know the origins of the email. Custom notification solutions allow for these types of configurations as well as localization capabilities and modifications to the layout.

Is there a dependency on your customers to resolve an issue? A custom notification can keep your customer informed of the importance of the issue and the urgency required to address it.

Using a custom notification solution like Jirassimo Emails Reminders & Notifications can fulfill your project communication needs and help you keep informed of the issues that concern you. It can be configured to support your desired layout or which fields you would like to share internally or externally. You don’t need to be a developer to do these configurations. Everything can be done by a JIRA or project administrator. 

JIRA is an efficient way to track and manage project activities and resource workloads. An add-on like Jirassimo Emails Reminders & Notifications can be beneficial for your project and help keep it on track.