Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

  • 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 and so that you can handle them as desired (map them or ignore them)appropriately.

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

...

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

Step 1 - Choosing and filtering data

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

...

  • 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.

Step 2 - Workflow mapping

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

...

Note

Unmapped statuses can mean missing information in your analytics
We have had customer support requests regarding inaccurate data that were a result of statuses not mapped to an ActionableAgile workflow stage. As we deal with historical data we have to map all of the workflow statuses involved with work you’re analyzing, not just current workflow statuses. This step will give you a way to learn about the unmapped statuses in your board’s data.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 field selection

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

...

Info

Please note there is no more “Select All” option. There are significantly more options available now and adding them all can cause performance hits. You’re also not likely to really use all of the data available to you. Therefore, take a few seconds to choose the items you really want because, with saved configurations, you don’t have to choose this every time! (smile)

...

During the beta period we have a “Share your thoughts” link in the feature. Please provide tips about what works, what doesn’t work like you expect and how we can improve. Also let us know if something is missing or unclear in this documentation.

Thanks!

Legacy Loaders

Note

Load a board, Load a filter and Load a projects are now our legacy loaders, they have been replaced by Load Jira Issues. We highly recommend you to start using this loader as the legacy options will be removed later this yearin July.