Hi Team,
I am trying to enforce a rule in Jira where a specific due date cannot be assigned to more than a set number of tickets (e.g., 10).
Use Case Example:
Ten tickets already have their due date set to November 4, 2025.
When a user tries to create or update an 11th ticket and set its due date to November 4, 2025, this action should be blocked or prevented, forcing the user to choose a different date.
My Question:
Is there any native way in Jira to configure this kind of "quota" or "capacity" rule for the Due Date field? I have explored custom validations and automation but haven't found a built-in solution.
Is there any Jira Native that can help me out or any alternate way to do ?
Environment:
Jira Cloud (Please specify if you are on Server/Data Center)
Jira can't conditionally check upfront for existing issues or field information before an ticket is created.
Related to your request, why, what is the reason to prevent more then 10 issues with the same due date?
There can be reasons enough to have more issues on the same date, what if as en example the company has 11 new joiners on the same date, on of their accounts can't be created on that due date because you can only do 10 issues on that due date?
Thanks @Marc - Devoteam for your reply.
This is to manage the capacity of the team, for eg our finance team can do only 10 transactions per day as their team capacity is low. If 11th person raising request to finance team for same date, they need to wait until next day and the system should not allow to choose the today's date as already 10 tickets are planned for today.
Please let me know if this can be achieved in jira or marketplace apps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As far as I'm aware ootb this is not possible as on creation there is no way to see if there already are issues based on information in a certain field in existing Jira issues.
You could look at apps that extend workflow possibilities, like:
or Scriptrunner behaviours, this will require the purhase of Scriptrunner first.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.