We are trying to find a Number field Comparison in Jira.
For Eg:
Budget:
Total Value:
We wanted users to update it like Budet should not be above than the Total Value
Budget >= Total .
Is there any way that we can do this block when creating an Issue
There isn't anything OOTB that could prevent a custom field value from exceeding another custom field value. However, you could use Automation to notify when that occurs.
trigger: field change
condition: budget>=total
action: notify via email, slack, comment, etc
But the automation will only start working after the issue is created, right?
I want to block it during the creation itself.
Also what are the other ways we can achieve it.
Can we do it by Plugin or by any other api things
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Correct. Automation is after the fact requiring the user to correct the situation. You can check the Marketplace for options. I believe Scriptrunner Behaviors could do this but I have not tried myself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I’m from Forgappify and wanted to share that we’ve been working on a more flexible way to build conditions using Jira Expressions. This led to the Ultimate Validator (now in Beta), which is part of the Workflow Building Blocks for Jira app. It lets you use most of the power of Jira Expressions—but without writing code. Instead, you build conditions through a simple UI.
With it, the comparison of fields is quite straightforward. Here’s how the configuration for your case would look:
I hope it will help,
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ismael,
Welcome to the Atlassian Community!
I’m a Support Engineer at Appfire, here to assist you.
If you’re open to plugin suggestions for simplifying your process, I recommend trying JMWE for Jira Cloud.
With this, you can add a validator when the issue is created and build your own validator to compare both fields. See the sample images below.
For more details, you can check out our complete documentation here. If you have any further questions, don’t hesitate to reach out to our support team—we’re always happy to help!
Best regards,
Prosper
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.