Today, instead of giving a tip about programming, I am offering to help with anything related to programming for Jira.

Do you need to simplify your code by automatically injecting required instances into your objects? Dependency injection is the answer.

Let’s look at how you can do something with issues that are a result of a JQL search.

There are at least two ways how to update a custom field that I know of. Depending on your needs, choose whether you want to store a change record on issue history or not.

Normally, when you run atlas-clean command, you loose JIRA configuration and have to start over when you run your development instance again. Luckily there’s a way to keep both your JIRA configuration and log4j settings after cleaning the target directory.

Normally, when you click the Excel View in your report, you get a file named ConfigureReport!excelView.jspa. But what if you want a more user-friendly name that is recognized as an Excel file?

I’ve recently discovered a great tutorial for writing JIRA plugins - Kitchen Duty Plugin by a company called Comsysto Reply. It focuses on JIRA 7.

Reports in JIRA are grouped into four categories, when displayed on reports page. You can choose one of them, but at the time of writing this (JIRA 7.4), you cannot create your own category.

How to set your own thumbnail for custom JIRA report? I’ll show you in this post.

We needed to display JIRA report only in a certain project and for users in specific groups. The group part was easy, but getting current project’s key was not.

2019 update: The code below no longer works with later versions of Tempo. Seems like the link on Adaptavist site below has been updated, so you can try that one. However now I highly recommend using the official Tempo REST API. It is definitely more stable than trying to call Tempo objects directly. Don’t worry about the deprecated comment at the worklogAttributes JSON array. It works all right.