Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /mnt/serverpilot1_srv/shawnhooper/apps/shawn-hooper/public/wp-includes/functions.php on line 6114
Changing the Order of Releases in JIRA - Shawn Hooper Skip to content

Changing the Order of Releases in JIRA

At Actionable, we’ve been using Atlassian’s JIRA to manage issue and bug tracking for our platform.  One of the things that’s annoyed me occasionally about JIRA is the order in which releases show up in the “Affected Version” and “Fix Version” dropdown lists.

Screen Shot 2016-06-16 at 11.45.37 AM

I’ve seen the odd case where these get displayed out of order.  For example, in the screenshot above, my release 1.3.2 was showing above release 1.4.0, which

  1. didn’t make sense.
  2. was prone to an issue reporter clicking on the topmost item, assuming it was the most recent.

The Fix

Today, I accidentally stumbled on the fix.  If you go into the “Releases” tab for your project:

Screen Shot 2016-06-16 at 11.49.19 AM

you will notice that each release has an icon to the left of it that is made up of three horizontal lines (the “Hamburger Menu” icon”).  If you click and that icon, you can drag the releases up and down the list into any order you’d like.

This order is mirrored in the dropdown lists in the issue editor.

Handy!

 

 

 

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.