Required custom field: Error is displayed on transition

[Elena Kotsinova]

Hi All,

I need help in following case:

I setup custom field QA Assignee. It is a user picker and shows only users in role = QA for particular project and doesn't have default value.

I need this field to be required only when specific transition happens.

I put a validator on this particular transition (Fields Required (JSU))

When I move issue according the transition the custom field appears on screen and it is empty.  I fill in the field and on submit an error message appears that this field is required and form can't be submitted even user is selected.

The only way this works is if I open the issue for editing and add user in this custom field. After this I can do a transition without an error. 

Is there a way to make such custom field required only on specific transition?

[Matt Doar]

That should be working, we use JSU validators for making fields required on transitions in many workflows. Might be worth checking that there is only one custom field with that name, and see if it works with a different custom field type? If it's still broken then I think it's time to file an issue with the JSU support team.

[Matt Doar]

Try it without the role restriction as well?

[Elena Kotsinova]

Tried without role filtering - same issue.

[Elena Kotsinova]

@Matt Doar could you please advice where I have to file an issue for the JSU support?

[Denise_Wuethrich_beecom_products]

Hi @Elena Kotsinova Please create an issue here so our support team could help you: https://beecom-products.atlassian.net/servicedesk/customer/portal/3 . Thanks!

[Jack Brickey]

Elena that was in my earlier post.

[Jack Brickey]

Theory - I am wondering if the name you entered is actually correct. So when you began to type did autocomplete offer options and did you select from the option?

[Elena Kotsinova]

yes, I selected it from the picker. the name is correct

[Jack Brickey]

hmmm... and your sure this is a validator you have and not a condition. Sorry, just grasping here as I'm not seeing anything obvious. Maybe you could share some screenshots in hopes something pops for me. Workflow illustrating transition and validator.

[Elena Kotsinova]

Is this enough?

[Jack Brickey]

well dang it... I was scratching my head until I took a moment and looked at the tags on this post and I now realize you are on Server. I should have seen that from the start. :-(

So I really can't assist on this but I will ping other Community Leaders to see if they might be able to. Also, I would recommend reaching out to Beecom support 

[Dave Liao]

@Elena Kotsinova - can you (and/or a Jira administrator, if that's not you) confirm what version of JSU is currently installed in your Jira?

[Jimmy Seddon]

Also as a side note, I don't ever remember any of the workflow validators providing an "*" for mandatory fields in workflow transitions.

Can you check that you don't have this field set as required in the Field Configuration for this project.  That would prevent this from only being required during the transition.

[Elena Kotsinova]

@Dave Liao 

It is version 2.24.3

[Elena Kotsinova]

@Jimmy Seddon This field is not required in Field Configuration, because I need it to be required only during transition.

[Susan Hauth _Jira Queen_]

Hi Elena,

Is the user being properly entered during the transition.  I don't see an avatar for the user.  Maybe you could paste in what the field QA assignee in the issue view looks like when the user is specified?

You also said that you limited QA assignee to a certain role.  Did you do that via the set up in the custom field or via a step property?

Cheers,

Susan

[Elena Kotsinova]

@Susan Hauth _Jira Queen_ The user is selected from a list with users who are in role QA for the project.

I never seen avatar to be displayed on this custom field even when it works.

[Susan Hauth _Jira Queen_]

Hi,

Are you sure your field is set up correctly?  If it's a user picker, I think the avatar does show.  I have a customer user picker field tester.  Similar to your use case.  But this is how it looks on my screens: