--- title: "Identifying Blocked Work" canonical: "https://support.55degrees.se/space/SP/3928785816/Identifying%20Blocked%20Work" format: markdown --- [jira cloud & Data Center] [azure devops] [standalone] > Macro (refined-tabs) > > > Macro (refined-tab) > > Visualising **Blocked Work** in ActionableAgile® Analytics allows you to move from simply reporting on the past to actively managing the future. > > ActionableAgile® Analytics tracks **two** pieces of information in regards to Blocked Work. > > 1. **Cumulative** number of days a work item was blocked. > 2. Whether or not the work item is **currently** blocked. > > > ℹ️ Step *away* from the **Blocked Column ** > > ℹ️ > > ℹ️ Moving a work item into a separate [Blocked Column or state] on your Board and later moving it *back* to an [active] one creates *[Backwards Flow](https://www.55degrees.se/blog/post/moving-cards-backwards-on-your-kanban-board)*. This distorts your charts, artificially inflates Cycle Times, and masks your true amount of WIP by acting as a parking space to get around WIP limits. It also hides where the actual bottlenecks in your workflow are occurring: [https://www.55degrees.se/blog/post/5-common-mistakes-stalling-delivery](https://www.55degrees.se/blog/post/5-common-mistakes-stalling-delivery) > > > ℹ️ We count **full** or **partial** days as Blocked Days except for when you block and unblock an item on the same day. > > There are a limited number of ways that ActionableAgile® Analytics can recognise if an item is blocked and how long it has been blocked for. > > Below is a quick overview of whether or not your blocked method is compatible with your version of ActionableAgile® Analytics. > > | | **Jira Cloud & Data Center** | **Azure DevOps** | **External Upload ** | **Trello** | > | --- | --- | --- | --- | --- | > | **Native Flag or Tag** | Use Jira’s native flagging system🚩. | Use Azure DevOps' native tagging system and name it `Blocked` or `blocked`. | | The Blocked Label Trello uses to identify Blocked Work is not supported by ActionableAgile® Analytics. | > | **Spreadsheet Blocked Column** | | | When creating your CSV, XLS, XLSX or JSON - if there is a column name called “Blocked Days” (case insensitive) and has a valid numerical value (a whole number), it will be identified as Blocked data.
[https://support.55degrees.se/space/SP/3924886383/Upload+External+Data#How-We-Identify-&-Map-Your-Data](https://support.55degrees.se/space/SP/3924886383/Upload+External+Data#How-We-Identify-&-Map-Your-Data) | > | **Custom Field** | ActionableAgile® Analytics **does not** recognise custom indicators or custom states for tracking Blocked Time. | > > By leaving the work item in the exact column where it became [Blocked] and applying the appropriate flag or tag, your board will provide a clear visual signal of the blockage, and ActionableAgile will accurately measure the delay without disrupting your workflow data. Remember to remove the flag or tag once the work is unblocked so work can proceed. > > > Macro (refined-tab) > > [jira cloud & Data Center] > > Users of ActionableAgile® Analytics in Jira Cloud and Data Center will need to utilise Jira’s native flagging 🚩 system to view blocked work and blocked insights in the app. > > | ![Screenshot 2026-07-23 at 16.30.45.png](media://47633b96-55c9-49fb-b578-bf372eab0401) | ![Screenshot 2026-07-23 at 16.31.31.png](media://959bca3e-9145-4790-bc26-6e733ee08b48) | ![Screenshot 2026-07-23 at 16.33.49.png](media://343ec5f8-ce2a-4e44-b9fb-aab55e344d4f) | ![Screenshot 2026-07-23 at 16.31.58.png](media://9318a687-0f3b-40b4-bda3-d8ac84d69fa6) | > | --- | --- | --- | --- | > | 1. Add Flag - On your work item, select the meatball menu and click [add flag]. | 2. Add Comment (Optional) - Your work item will immediately be flagged and you’ll instantly be greeted with the option to add a comment regarding why the flag was added. The comment is not needed for us but may be useful for you. | 3. Blocked Item - The work item will show as Flagged and thus Blocked | 4. Remove Flag | > > > > > Macro (refined-tab) > > [azure devops] > > Users of ActionableAgile® Analytics in Azure DevOps will need to utilise Azure DevOps' native tagging 🏷️ system to view blocked work and blocked insights in the app. > > | ![Screenshot 2026-07-27 at 15.03.50.png](media://82217b5d-e2ce-478b-b0cb-fc3421362bfd) | ![Screenshot 2026-07-27 at 15.05.59.png](media://600c0cb8-02a2-44ed-969f-310b9b724716)
![Screenshot 2026-07-27 at 15.06.38.png](media://87c60779-e3e2-4138-9b1c-38ea566de40e) | ![Screenshot 2026-07-27 at 15.07.10.png](media://03223d31-838a-4650-b987-94ef22f8e21e) | ![Screenshot 2026-07-27 at 15.08.00.png](media://c715d0f0-100c-462e-aef2-ede00a61c531) | > | --- | --- | --- | --- | > | 1. Add Tag - On your work item, select the meatball menu and click [add tag]. | 2. Name your tag `Blocked` or `blocked` and save the changes. | 3. Blocked Item - The work item will show with the Tag `Blocked` or `blocked`. | 4. Remove Flag - Select the [x] next to the Tag to remove it. | > > > > > Macro (refined-tab) > > [jira cloud & Data Center] [azure devops] [standalone] > > When you upload an external data file through the external data loader, include these two columns *immediately* after your workflow stages: > > | | | > | --- | --- | > | Blocked Days | Blocked | > | A whole numerical value of how many days the item was blocked e.g. 5. | Whether the item is currently blocked e.g. True or False. | > > Please refer to [https://support.55degrees.se/space/SP/3924886383/Upload+External+Data](https://support.55degrees.se/space/SP/3924886383/Upload+External+Data) for further details. > > > Macro (refined-tab) > > [standalone] > > > ℹ️ The Blocked label 🏷️ in Trello is **not supported** in ActionableAgile® Analytics. > > ![image-20260727-132133.png](media://90d79c11-100d-4936-999d-c75da1e04341)