'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Create an Azure DevOps Rule Based on Due Date and State
Question details
The user wants to configure a rule in Azure DevOps to set Urgency to 1 when a work item is BLOCKED, Priority Level is 1, and the Due Date is earlier than the current day, but the Due Date field is missing from the conditions list.
- Product
- Azure DevOps
- Device & OS
- not provided
- Scenario
- Creating a custom rule to automatically update work item urgency based on blockage status and missed deadlines.
- Observed behavior
- The Due Date field is not available in the rule condition dropdown, preventing the configuration of the desired automation rule.
Verify your current Azure DevOps process template (Agile, Scrum, CMMI, or Basic) in Organization Settings and ensure you have the necessary project collection administrator permissions to edit work item rules.
Check Field Support and Process Template Limitations
Determine if the Due Date field and dynamic date comparisons are supported by your current Azure DevOps process rules.
Azure DevOps has specific constraints regarding which fields can trigger rules. Currently, comparing date/time fields against dynamic values like the current date (@Today) is highly restricted in standard work item rules.
Navigate to Organization Settings > Process and select the process template your project is using.
Select the specific Work Item Type (e.g., Bug, Task) you are trying to modify, and click on the Rules tab.
Attempt to create a new rule and check the 'When' condition dropdown to confirm if any date-based fields are natively supported for your setup.
Seek Assistance or Request Features in Microsoft Q&A
Since the condition cannot be configured natively, reach out to the Azure DevOps community for advanced workarounds.
Need a Lightweight Alternative for Project Documentation? Try WPS Office
While you use Azure DevOps for project tracking and automation, you still need reliable software for drafting specifications, reports, and spreadsheets. WPS Office is a completely free, lightweight alternative to Microsoft Office that easily handles all your project documentation needs.
Frequently Asked Questions
Why is the Due Date field missing in Azure DevOps rule conditions?
Azure DevOps imposes strict limitations on which fields can be used to trigger rules. Date and time fields, especially when needing to be evaluated against dynamic dates like 'Current Day', are often unsupported in standard process rules to prevent continuous background polling.
Can I use Power Automate to update work items based on Due Date?
Yes. Since native DevOps rules lack this feature, you can create a scheduled cloud flow in Power Automate. The flow can query Azure DevOps daily for work items past their due date and automatically update their Urgency or State fields using the Azure DevOps connector.
How do I find out which process template my Azure DevOps project uses?
Go to your Project Settings in Azure DevOps, select Overview, and look for the 'Process' field under the Project details section. This indicates whether your project uses Agile, Scrum, CMMI, or a customized inherited process.
