v3.x and earlier: Loading Data in Jira Server and Data Center

The new data loading module allows you to load from boards, projects, or issue filters based on your desired date ranges and other available criteria.

Want to revisit that same data later? No problem! Want to make tweaks to the data being loaded? You can do that now too. Read on for more details.

Jump to:

User benefits

  • Ability to save data loading configurations so that you don’t need to configure your data each time you want to view it in ActionableAgile.

  • The ability to see how your Jira workflow statuses are mapped in your Jira boards. Specifically you are able to see what unmapped Jira workflow statuses exist so that you can handle them appropriately.

  • Ability to filter issues by resolved date in addition to created date

Additional Notes

  • ‘Check for updates’ is no longer used for this feature. Instead, click Go next to the saved data set you want to load.

 

How to enable it

With this new release, the new data loader will not be available until it has been enabled by the Admin. To do so, go to Manage Apps->Global configurations. Here you’ll find a new section: “New Jira issue loading experience”.

The new data loader is available in these versions of ActionableAgile for Jira:
Server - 3.10.0 or later
Data Center - 3.10.2.dc or later

Create a new data set

To use this new feature once enabled, click on the option “Load Jira Issues” from the folder menu.

The new board loading experience will launch. It has 3 steps:

Step 1 - Define the data you want to analyze

Choose your data source (board, filter or projects) and any filters limiting the data (ie. only resolved after X date) that should be imported.

To start, choose the Jira issues you’d like to load from the dropdown. By default, the dropdown will show available boards, projects, and filters. You can uncheck up to two of those types to filter the available options. You can type in the field and the list will begin to filter down as you type.

 

Once you select an option, you’ll see how many Jira issues were found for that selection.

 

In the right column, as seen in the image above, you have options to filter down the items we pull from your selected board, project, or filter. As you choose to filter by created date, resolved date, or other available filter, you will see that the number reflecting matching Jira issues for your search will change to reflect your choices.

Finally, click the Next button in the bottom right-hand corner of the dialog.

 

Step 2 - Map your workflow statuses

We automatically import the mapping found in the board settings for the board you’re loading. However, sometimes there are statuses that aren’t mapped and this can cause various issues with your analytics. In this screen, we give you the opportunity to review and decide how to proceed (map them or ignore them).

Working with the workflow mapper

  • If you are happy with the mapping as is, click ‘Next’ to move to step 3.

  • If you’d like to make changes, here are some things you can do:

    • Use drag and drop to move a Jira Workflow Status (the white items with a name and number) from one ActionableAgile Workflow Stage to another

    • Combine two ActionableAgile workflow stages by dragging one on top of another.

    • Delete an ActionableAgile workflow stage using the trashcan icon.

    • Click on an ActionableAgile workflow stage name to change it.

    • Add an ActionableAgile workflow stage using the + button above the unmapped workflow stages. It will be created at the very left. Drag it right to the correct location.

Why do I have unmapped statuses?

  • There are statuses in your current workflow sitting in the unmapped status area in your board configuration. Suggested solution: map these statuses in your board so your analytics match your board.

  • Your workflow has changed or issues have moved from one workflow to another. Certain statuses no longer exist in today’s workflow but exist in your issue’s history. This will likely be less of an issue as you generate new data and filter out older data. Suggested solution: map unmapped workflow statuses to existing workflow stages in our workflow mapper.

Unmapped statuses can mean missing information in your analytics
We suggest you map all workflow stages - either in existing columns or new columns - as leaving unmapped statuses can cause some issues with data rendering. You can always uncheck columns you don’t want to use from the workflow stages control in ActionableAgile!

Step 3 - Additional fields

See the default data fields we pull for each issue and choose additional fields to import for your dataset.

  1. Click on the dropdown to see a list of available fields for your dataset.

  2. Click on a desired field to begin creating a list of items to add.

  3. Once you have the items you want to load, click on the Add fields button to the right of the dropdown.

  4. When you’re satisfied that all fields have been added to the payload, click the FINISH button in the bottom right-hand corner of the dialog box.

 

Load a saved data set

Once you have used the board loader to configure and load data, you’ll notice that the most recently created configurations are available to load or edit.

 

You can currently save up to 10 configurations. Once you have 10, the next time you create a new configuration, by editing or creating one from scratch, the oldest one will be removed to make place for the new one.

 

Manage your saved data sets

You can currently do 3 things with these saved configurations:

  • Go - choose this to load this data immediately without revisiting the workflow or fields configuration. Filters you set for this data on step 1 will be honored.

    • Please note that we will put you in edit mode if we find new unmapped statuses that weren’t there when you originally loaded the data. New statuses will have a gold-colored border. Continue through steps 2 and 3 to load your data.

  • Edit - save time by using a saved filter as a starting point. Change what you need. The result will be a new saved configuration (it doesn’t override the one you edited).

  • Delete - Delete configurations you no longer need so that they don’t take up one of 10 available slots. If you want to delete a favorite configuration, click the star to remove it from your favorites and you will then be able to delete it.

Load external data

You have the opportunity to load a csv file as normal.

Load example data

You can always load the example data from the data set dropdown as well.

Legacy Loaders