Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,464,836
Community Members
 
Community Events
176
Community Groups

Difference between condition and validition

Differnce between condition and validation 

3 comments

Conditions are checks that are done on the current issue status, that will decide whether a workflow transition is shown or not. For example:

  • is this current user a member of the role that is allowed to execute this transition?
  • is the value of a custom field permits me to execute a transition?

Validations are checks that are done when you execute a workflow transition (usually checks are done when an associated screen is shown). For example:

  • have I entered all the required fields in the workflow transition screen?
  • have I updated a field in the workflow transition screen, which allows me to progress thru a transition?
Like # people like this

In a slightly simpler terms, conditions are evaluated even before the issue is shown to the user to decide if a workflow transition is valid for the user. 

Validations happens once the workflow transition is triggered when the user submits on the workflow screen. 

Like Martin Gregory likes this

With the conditions, the button does not appear until they are met.  With validators in the past if the field was required but is blank or something then a red asterisk appears next to the field which gives the user more feedback than the button not appearing.  If the field is not visible on the screen then what feedback is provided to the user? Anything useful?

We are running JIRA server v7.7.0.  A hybrid could also be used for validators of some things then conditions of others to hide the button until it is at least close to ready.  If more feedback is provided then I would be inclined to use validators more than hide the button so that the user is provided feedback.  Would at least help in troubleshooting advanced workflow checks when the user can't do something they want rather than them just saying they don't have the button.  The permission helper also isn't helpful with advanced workflow options when there are more options than just permissions.

Like # people like this

We have moved to using validators for exactly for this purpose - to provide a custom error message as hiding the button (or more recently hiding the drop down transition in the new view) doesn't guide the user as to what the problem is and how to remedy it.

Like # people like this

Comment

Log in or Sign up to comment