---
title: "Frequently Asked Questions (FAQ)"
canonical: "https://support.55degrees.se/space/SP/3928326145/Frequently%20Asked%20Questions%20(FAQ)"
format: markdown
---
[jira cloud & data center] [azure devops] [standalone] 

> Macro (refined-tabs)
> 
> > Macro (refined-tab)
> 
> > ✅ Core concepts apply across all versions: clearly define when work starts and finishes, avoid backwards-flow columns, and use Workflow Stages to control calculations.
> 
> ### 🇶 How is Cycle Time calculated?
> 
> 🅰️ Across all versions, Cycle Time is the inclusive difference between the date an item enters the first selected workflow stage and the date it enters the last selected workflow stage. The Workflow Stages control lets you include or exclude stages to define start and finish precisely. [https://www.youtube.com/watch?v=JtnVsWmOsIs](https://www.youtube.com/watch?v=JtnVsWmOsIs) 
> 
> ### 🇶 Can I define my own start/finish (Workflow Stages)?
> 
> 🅰️ Yes. Use the Workflow Stages control to choose which stages are included. The first selected stage marks “started”; the last selected stage marks “finished.” Adjusting selections updates all charts accordingly.
> 
> ### 🇶 Do weekends inflate your Cycle Time?
> 
> 🅰️ [No](https://www.youtube.com/watch?v=C9DbPe-5bgQ). We include weekends in forecasting and cycle time calculations because flow metrics measure **total elapsed time, not active working time**. Using calendar days provides a much truer, clearer, and more predictable way of looking at your process for several key reasons:
> 
> - **It speaks the language of the customer:** Customers do not calculate your internal working hours, weekends, or holidays. When you tell a stakeholder an item will take 15 days, they expect it in 15 calendar days; failing to include weekends creates significant misunderstandings and frustration.
> - **Excluding weekends actually makes your forecasts worse:** While it seems intuitive that excluding weekends would make numbers more precise, the math proves otherwise. If you exclude weekends from your cycle time, you also have to exclude them when projecting forward. This arbitrarily adds days back into your timeline, making **every single forecast that excludes weekends longer and less accurate than those that include them**.
> - **It distorts your risk profile:** If you try to create a forecast targeting the 85th percentile using only "working days," you will likely find that you are actually planning at a much higher, more conservative rate, such as the 89th or 90th percentile. This means you are taking on a different risk profile than you intended, which can lead to poor economic and planning decisions.
> - **It prevents mathematical nightmares:** Stripping out non-working days makes the math unnecessarily complex. You would have to account for different international holidays, varying geographic definitions of a weekend, vacations, and sick days. Furthermore, spreadsheet tools like Excel struggle with this, often creating off-by-one errors because of how they handle inclusive versus exclusive date counting.
> - **Your historical data already accounts for "life":** Disruptions like weekends, holidays, meetings, and illnesses are an inevitable part of any system. By incorporating all calendar days, **your historical data naturally bakes all of these realities into your probabilistic forecasts**, allowing you to answer "When will it be done?" efficiently without needing to continuously do manual math adjustments.
> 
> ### 🇶 How does the app handle work moving backwards in the workflow?
> 
> 🅰️ If an item enters a stage multiple times, the timestamp used is the last time it entered that stage. Moving an item backwards conceptually invalidates the previous forward movement; time is effectively merged into the current earlier stage. This preserves a consistent, non-decreasing Cumulative Flow Diagram.
> 
> ### 🇶 Can I use a “Blocked” column?
> 
> 🅰️ Avoid a separate “Blocked” column. Keep the item in its current workflow stage and mark it as blocked (via flags, tags, or attributes depending on platform). This preserves flow visibility and enables accurate blocked-time and flow-efficiency calculations.
> 
> ### 🇶 Which Agile methods are supported?
> 
> 🅰️ Any method with a defined workflow works (Scrum, Kanban, Scrumban, SAFe, etc.). Success depends on clear entry/exit criteria and consistent movement through sequential stages. For Scrum, avoid bulk-starting and bulk-finishing all work only at sprint boundaries.
> 
> ## Troubleshooting and Tips
> 
> - Jira: If the app loads blank, disable ad blockers for [atlassian.net](http://atlassian.net/) and reload.
> - Avoid a rightmost “Blocked” column; it can interfere with finish detection.
> - Use the Source Data chart to inspect imported timestamps, blocked days, and mapping effects.
> 
> > Macro (refined-tab)
> 
> 🇶 Where do I access ActionableAgile® Analytics in Jira?
> 
> 🅰️  Use the app entry points documented here: [https://support.55degrees.se/space/SP/3988652036/App+Location](https://support.55degrees.se/space/SP/3988652036/App+Location) 
> 
> 🇶 How does the app determine “Done” in Jira?
> 
> 🅰️ “Done” is based on entering the last selected workflow stage, independent of Jira status names, states, or resolutions. You control which stages count via Workflow Stages.
> 
> 🇶 Does it work with Scrum?
> 
> 🅰️ Yes, but avoid patterns that start everything on sprint day one and finish everything on the last day. Monte Carlo forecasting uses historical daily throughput—irregular patterns reduce forecast quality. 
> 
> If you cannot avoid bulk-finishing, but you do use a status/column such as “Release Ready” where work is moved when it is finished but not released, use this as you end-point instead. 
> 
> 🇶 Which custom field types are supported?
> 
> 🅰️ Common Jira fields are supported (e.g., story points, labels, select/multi-select, user pickers, sprints, epics, versions, etc.). If a field doesn’t appear during loading step 3, confirm its type with a Jira admin and contact support if needed.
> 
> 🇶 How is blocked work identified in Jira?
> 
> 🅰️ By Jira’s native “flagged” status. Blocked days include partial days except when blocked and unblocked on the same calendar day. [https://www.youtube.com/watch?v=j0EBha6hJcc](https://www.youtube.com/watch?v=j0EBha6hJcc) 
> 
> 🇶 Do I have to reload data every time?
> 
> 🅰️ For structural changes or newly added boards/projects/filters, you will need to refresh you data set as we do not store your Jira data, only the configurations in the local storage. 
> 
> 🇶 Can I rename Epic to Feature?
> 
> 🅰️ Renaming the issue type won’t negatively impact ActionableAgile® Analytics, however migrating or deleting boards that are used by a saved data-set can cause the data set to corrupt as the Jira ID’s no longer match or exist. Delete the data set and create a new one. 
> 
> 🇶 Where can I configure and map workflow statuses?
> 
> 🅰️ When you create a data set, you need to map your data. You can also edit the mapping at any time. [https://www.youtube.com/watch?v=jwYksLOVyY0&pp=0gcJCZEKAYcqIYzv](https://www.youtube.com/watch?v=jwYksLOVyY0&pp=0gcJCZEKAYcqIYzv) 
> 
> #### Jira Licensing and Billing
> 
> 🇶 What are your rules around trial periods? 
> 
> 🅰️ Jira Cloud has a 30-day trial which can be extended by contacting us in via our [Support Portal](https://support.55degrees.se/) or at [support@55degrees.se](mailto:support@55degrees.se) and Data Center has a 30-day trial renewable up to 5 times (via Atlassian).
> 
> 🇶 Do I need to license all Jira users?
> 
> 🅰️ Yes - Atlassian Marketplace licensing is tiered by total Jira users. ActionableAgile® Analytics pricing for Jira is discounted to offset this. [https://www.55degrees.se/products/actionableagileanalytics/pricing](https://www.55degrees.se/products/actionableagileanalytics/pricing) 
> 
> 🇶 Quotes, invoices, and payment cadence
> 
> 🅰️ Quotes & Invoices are handled by Atlassian Marketplace; payment cadence follows your Jira subscription. Discount coupons may be available for purchases made through our approved Marketplace Partners. [https://www.55degrees.se/partners/directory](https://www.55degrees.se/partners/directory) 
> 
> 🇶 Data Center compatibility, updates and end-of-life support?
> 
> 🅰️ Yes, ActionableAgile® Analytics is supported for Jira Data Center. We will continue supporting Jira Data Center customers throughout Atlassian’s end-of-life timeline. Core updates such as charts, insights, and calculations will still be delivered.
> 
> Some features require extensive development and testing that are specific to the Data Center platform. With Atlassian planning to sunset Jira DC, it’s important for us to focus resources on updates that bring the greatest long-term value to customers across platforms.
> 
> Platform-dependent updates — such as native Jira dashboard gadgets or certain integrations with Jira internals — may not be delivered to Data Center. Instead, we’re prioritising improvements to the ActionableAgile® Analytics experience itself, which will benefit both Data Center and Cloud users.
> 
> 🇶 Can you help us migrate ActionableAgile® Analytics from Data Center to Cloud? 
> 
> 🅰️ We will be ready to support you with a smooth transition when that time comes. ActionableAgile® Analytics for Jira Cloud includes the same core capabilities and ongoing innovation.
> 
> #### Jira Data Residency
> 
> 🇶 Which locations do you support for Data Residency in Atlassian Jira? 
> 
> 🅰️ Supported data residency locations include Sweden (Stockholm), USA (North Virginia), and Australia (Sydney). New customers after the platform expansion can choose among these regions; earlier customers remain in Sweden. Data migration between regions is not yet supported and is on the roadmap.
> 
> 
> > Macro (refined-tab)
> 
> 🇶 How do I install the extension?
> 
> 🅰️From the Visual Studio Marketplace listing for ActionableAgile Analytics, select Get and follow the prompts to install to your organisation. A 30-day fully functional trial is provided.
> 
> 🇶 How do I access it after installing?
> 
> 🅰️ Go to Azure DevOps ([dev.azure.com/yourorganization](http://dev.azure.com/yourorganization)) → select a project → Boards → ActionableAgile Analytics. You can load any project from within the extension regardless of the entry project.
> 
> 🇶 Who can use it (permissions)?
> 
> 🅰️ Users with Stakeholder access cannot view/edit Analytics views and therefore cannot use ActionableAgile. Ensure appropriate access levels.
> 
> 🇶 Do licenses span multiple Azure DevOps organisations?
> 
> 🅰️ Licenses are tied to user/organisation pairs. Using ActionableAgile across two ADO organisations requires licenses for each.
> 
> #### Azure DevOps Pricing and Licensing
> 
> 🇶 Models
> 
> 🅰️ Per-seat or organisation-wide licensing. Per-seat can be monthly or annual; organisation-wide is annual via invoice and priced by org size/count.
> 
> 🇶 Indicative pricing
> 
> 🅰️ Per-seat reference: $20/user/month or $200/user/year. Organisation-wide: price varies by size and number of organisations—request a quote via support.
> 
> 🇶 Payment methods
> 
> 🅰️ Monthly per-seat: credit card via billing portal. Annual: credit card via portal; invoice available for subscriptions with at least 5 users.
> 
> #### Azure DevOps Data Loading and Workflow
> 
> 🇶 Should I load by Board or Work Item History?
> 
> 🅰️ By Board = single board’s data; By Work Item History = broader, multi-team/historical view. Use mapping to align legacy columns/states.
> 
> 
> > Macro (refined-tab)
> 
> 🇶 What is the Standalone version and how does it work?
> 
> 🅰️ A browser-based app that runs locally; your data is not transmitted to or stored by the vendor. Load data via CSV/XLSX/JSON, or import from Jira/Trello using wizards.
> 
> 🇶 How do I start a trial and learn the basics?
> 
> 🅰️ [https://analytics.actionableagile.com/](https://analytics.actionableagile.com/)
> 
> [https://actionableagile.com/index.html#quick-start](https://actionableagile.com/index.html#quick-start)
> 
> #### Standalone Pricing and Licensing
> 
> 🇶 Models and payment
> 
> 🅰️ Per-seat (monthly or annually) or domain-wide (annual via invoice). Monthly per-seat via credit card; annual via card or invoice (for 5+ users).
> 
> 🇶 Indicative pricing
> 
> 🅰️ Per-seat reference: $20/user/month or $200/user/year. Domain-wide pricing varies by domain size—request a quote via support.
> 
> #### Standalone Platform Notes
> 
> 🇶 Can the app track blocked time when loading a Trello Board? 
> 
> 🅰️ Blocked time in Trello is not currently trackable; consider alternative indicators or process policies for visibility.