-
Bug
-
Resolution: Fixed
-
Highest
-
29
-
Severity 3 - Minor
-
52
-
Issue Summary
Users won't be able to create child issues via Add a child issue or + inline under Epic if you have a workflow validator in creat transition for a required field.
Steps to Reproduce
- Add Field Required Validator in the create a transition in the workflow
- Go to Epic and click on Add a child issue or + inline to create a child issue
- It won't bring up the screen and give an error cant create the issue because of the required field is not entered.
Expected Results
To popup the screen to be able to enter the required fields
Actual Results
It gives an error " We could not create the child issue must add < field name>"
Workaround
1) Make the Linked issues field required in the Field Configuration
2) Add the Linked issue field to the screen
This forces the create issue screen to pop up to be able to add the required fields. Although the Linked issues field is set to Required it does not do the check and allows us to not enter any value and won't set it. You may examine the issue via rest api:
https://<instance.atlassian.ent/rest/api/3/issue/issuekey-xxx shows the issue links are empty as we wish.
OR
Remove the validator from creating transition and make the actual fields as Required required in the field configuration.
- is related to
-
JRACLOUD-72506 Creating/Adding Child/subtask should allow selecting any project
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-80148] Wont be able to create child issues under Epic if you have workflow validator in create transition
If validations for create transition isn't going to be fixed, then I don't think it should be possible to use validations for the create transition. I understand if this isn't easy to fix but having a feature that isn't working with no plans to fix doesn't sound like a very good idea, especially as there are fields such as Team that you can't make mandatory so it is only in transition where we can prompt user to set that information.
@Michele Routon, maybe you could set the Description field as Required in your Field configuration. Not a big deal to have it mandatory and it will make the creation screen appearing...
Unfortunately, the first option for the workaround does not seem to work as I get an error that the Linked Issue is required when trying to create a child. Option 2 is not viable for us as our requirement is that either our custom field is entered or a user has to be a member of a certain group.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team
Hello,
I think the severity and piority should be higher for this bug. All users create child issues, and unable to di it just because there are field required validator is a huge inconvenience.
We share the share the same field configurations for multiple projects. Creating new field configurations for every workflow/issue type is not efficient at all 
I totally agree, I been waiting for a solution as my team are using the work around but they want to keep this work flow too
I believe the priority should be higher than low, as there are many users that have workflow validators and creating child tickets from an epic is a great time saver.
This is now rolled out to 100% of tenants