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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Fix version field validation

i need help to solve this ,

-when Fix versions/s field is edited  it should select values which belongs to circle ones ..see in below  picture

-if the option which contains " . " ex( is selected give error message "cant assign this fix version"  .



1 answer

0 votes

You'll need to fix whatever it is that is checking for the . in the name and remove it so that you can add the valid versions.  Jira doesn't do this natively, so it looks like you have a broken Behaviour (as you mention that)

Hello @Nic Brough -Adaptavist- ,

It's a pleasure read you again! I hope you are doing well.

We want to do this using Behaviours of Scriprunner.

Can be?

Best regards!

Hi Juan,

I am sorry, I am confused.  I think I have misunderstood the original question.

Could you help me out by describing what you are trying to achieve directly?  Instead of "this is not doing what we want" (which I have struggled with), maybe describe what should happen?

For example (and this is my next guess on what I am not understanding): In your screenshot, there is a list of possible versions to select from.  You would like to remove items from that list so they cannot be selected (even though they are valid)



Yes, I think is not easy to explain because we implemented complex scenario but, the only that we need by the moment is avoid the possibility of set an specific version.

It means.

We have a project with version A, B, C.

The first condition that we want to acomplished is that "for the issue X" the version B can never be selected.

Is this possible with behaviours? 

Sorry for inconveniences.

Thanks in advance.

Best regards.

Yes, shortening the list of versions can be done with Behaviours - this is the baseline script I usually start from when I am looking to do it:

However, I'm no Behaviours wizard, I don't know if you can do a condition of "for issue X" (although that does depend on how you want to make the decision - could it be based on the issue type as an easy example?  Something like "Can't select version 12345 for bugs")


The decision is going to be selected by some "customField of the issue" so I think can be done but...the problem is other now I think so.

Maybe we can implement this solution to reduce the list of options in the issue view screen. That's good! is a good solution in this case. Thanks! actually we did in the past.



Why this is not a good solution for us now...We need that this condition works in Agile board...

It means that, when the user drop the issue to the "incorrect version" the issue fix version shouldn't be modified. If is empty remain empty, if has a value keep the previous value.


Make sense? :)


I think in this case, the solution will be doing in a listener, when the issue is trying to set the version B for the issue X, "do nothing", isn't it?


Thanks a lot for this conversation, has been very productive!


Best regards.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events