The Tip of the Month, brought to you by Atlassian University, is a monthly series to help master Atlassian tools. Products are more fun to use when you know all the tricks.

Smaller tasks mean more issues

Hey JIRA Agile (formerly GreenHopper) users. One of the key tenets of agile is to ensure that work is divided into small-enough chunks so that the team can reliably estimate and complete work predictably. Breaking down a complex task into sections that are easy to estimate is critical for the health and success of any agile team. However, a pitfall that comes with this methodology is that it can generate larger numbers of tickets for individuals to deal with. This month we have a simple tip to help you work with larger sets of issues more efficiently in JIRA Agile.

Do more with less: bulk change!

Many of you know that JIRA Agile makes it easy to drag-and-drop issues to assign to an epic or a version. You can select multiple contiguous issues by clicking the first issue, holding down the shift key and clicking the last issue. To select issues that aren’t next to each other just hold down the control (Windows) or command key (Mac) and select the issues individually. You can then drag the issues over an epic or a version to assign all of the issues to that epic or version at once.

 

jira_agile_bulk_change_epic

When dragging a set of multiple issues, JIRA Agile shows an indicator in the upper right-hand quarter noting the number of issues affected by the change. Also, the selected epic will be highlighted as shown in the example above.

What if you want to change some other attribute of those issues aside from version or epic? The right click menu has an option for “bulk change.” Bulk change applies the same operation to several issues, such as changing the assignee or component, adding a custom field, or performing a workflow transition like resolve. To perform a bulk change, select the issues you would like to change and then right click to select bulk change.

 

jira_agile_bulk_change_wizard

The bulk change wizard will walk you through the change process through an easy-to-follow wizard. Super simple.

Pro Tip: Keep in mind, JIRA sends notifications on changes. Bulk changes can trigger anywhere from tens, to hundreds, to even thousands of emails being sent to your team. The bulk change wizard has an option to not send email on change. It is a best practice to use discretion when sending email around bulk changes. It can be more efficient to send the team one email notifying them of the change and not have JIRA send change emails. To learn more about using notifications effectively check out my two blogs on the subject: Using watchers and @mentions effectively and Meet the New JIRA: Watch Issues in Bulk!

If you found this helpful, please visit Atlassian University – interactive tutorials and videos with tons of tips just like this one.

About Dan Radigan

Software has been a passion since the days of the floppy disk (you know, the actual 5.25 inch floppy ones). Agile has had a huge impact on me both professionally and personally as I've learned the best experiences are agile, both in code and in life. You'll often find me at the intersection of technology, photography, and motorcycling. Find me on twitter @danradigan.

View all posts by Dan Radigan »