nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ERROR: 6MNAK3 when creating issue from standard board roadmap due to field required validator.

Brinda Tailor

I am getting ERROR: 6MNAK3 when I try to create child issue of an epic in the board roadmap after I added a field required validator to the standard issues (Story, bugs, tasks) workflow. Can someone advise on any workarounds or solutions to this problem?

The team field is custom locked field by Jira, which is why we are unable to make it a required field.

Accepted answers

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

This error is more of a reference for Atlassian to search for in logs and data, and to group together the errors when they happen on different Cloud systems. It's not representative of the actual error that is causing you a problem.

Could you show us the configuration of the validator, explain what actions you take to get it thrown, and the full text of the error page?

Brinda Tailor

Screenshot 2022-04-21 100454.png

Nic Brough -Adaptavist-

Oh, that's your validator working. You must have left the team field blank when you transitioned the issue.

Brinda Tailor

Thanks for replying! When I create a child issue from roadmap, I don't get an option to add team field, just adding the summary and creating enter throws this error.

Unlike that, when I create an issue in the backlog, I get a create issue pop-up which then lets me add the required field.

Brinda Tailor

Configuration of validator:

Screenshot 2022-04-21 101128.png

Actions:

After saving the workflow with this validator, I go to the project board roadmap, create a child issue under an epic:

Screenshot 2022-04-21 101349.png

And then get this error:

Screenshot 2022-04-21 100454.png

Nic Brough -Adaptavist-

Ok, then this is working as intended. The roadmap does not do "asking for optional data" when creating child issues, so you have nowhere to enter it. Then your validator is checking on a field you can't enter, so it's going to have to return a failure. The error code is just the validators tag for the config that is causing a problem.

I'm afraid all you can do is accept that Team should be optional, or continue to block child issue creation from the roadmap.

Craig Nodwell_7eve9b

I can see what you are doing based on this page:
Create Child Issue in Roadmap View

Couple of quick questions.
1. If you turn off the validator what gets copied to the child? -> do all shared fields with a new summary get copied?
2. Is that field on the parent issue? -> maybe putting it there and with a value..

Brinda Tailor

Hi Craig,

Thanks for responding! I have turned off the validator as it was causing multiple problems. Currently, nothing gets copied when I turned off validator. Also, that field is on the parent issue but there might be some cases where multiple teams work towards the same epic.
Thank you for the suggestion though!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

validator

error