Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Field Validator in Create Transition not working with Advanced Roadmaps

In the Create transition I added a validator that a field must not be empty. This works fine in Jira, but not in Advanced Roadmaps. The field is on the Advanced Roadmaps grid and has a value in the corresponding row, but the value does not seem to be recognized. When I try to "save the changes in Jira" from the Review Changes button in Advanced Roadmaps, I get an error that the field must have a value.

1 answer

0 votes
Dave Atlassian Team Apr 23, 2021

Hi @David Wuth,

Just to clarify - you're entering a value for the field in the plan, but you're still getting the required field modal popping up when you attempt to save the changes? Which field have you created the validator for? Is this a custom field? If so, which type? Are you seeing the value showing up in the Review Changes dialog?



I have the issue with two fields. One is a custom field (single choice drop down), the other is the Jira Teams field.

BTW, I had previously found JSWCLOUD-19311 as a bug that describes exactly what is not working for me (both the custom field and Teams field). Seems that Atlassian does not want to fix this...

Like Dave likes this

Thanks for sharing that link @David Wuth ...I've had a look through and I noted that it was originally marked as for the Live Plans interface (which will no longer be available after July 31st) this year. It was closed due to the age and lack of interest ... it's not a question of "wanting" to fix bugs, we want to fix all bugs - it's just that the reality is that it's not possible to fix everything due to resources available, we also have to consider the cost, risk and impact of making any changes - this is nothing unique to Atlassian. The bug was closed as "Won't Fix" because nothing had happened with it in 4 years and it was marked as being a problem on a deprecated interface. Our aim with closing it was to improve transparency and set clearer expectations.

However it does look like that bug can be reproduced on the new interface, so arguably this could be re-opened and the description updated ... that unfortunately doesn't necessarily mean that it will be scheduled for an immediate fix, and I wouldn't want to give any false hope that it would. I'll look into this more next week - if you haven't already I would definitely raise a support request as that does have an impact on priority ranking of bugs.



Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

244 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you