You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
is it possible to block the change of a field if another field is not filled?
We want that if the "Description" field is empty, we cannot put an assigner.
One approach you could try that doesn't involve automation is an Assign transition:
Of course, a user can satisfy this validator by typing "N/A", so this kind of enforcement is no substitute for a team that understands why it's important to include a useful description that includes the relevant information that the assignee will need in order to get the work done.
@Kelly Arrey Hi
it's an interesting idea, but I don't fully understand how to implement the dependency.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Іван Андрєєв, which parts are unclear? Are you working in a company-managed project or a team-managed project. Do you have Jira admin permissions or does someone else do your Jira administration?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
automation is not suitable for my management because you have to refresh the page to see the changes and the specialist may just think that he has appointed, but no. Here it is necessary to somehow forbid him from this action immediately, so that he has no choice. Block action.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Іван Андрєєв ,
I am thinking of two possible scenarios here:
1. Put a validator in the Workflow, i.e. the Description field will be required
2. Build an automation like this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
automation is not suitable for my management because you have to refresh the page to see the changes and the specialist may just think that he has appointed, but no. Here it is necessary to somehow forbid him from this action immediately, so that he has no choice. Block action.
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.