Hi all,
I have an issue when creating a task under an epic - you know, the plus button that requires only the title. The problem is, that there is a mandatory field, which breaks the issue creation.
I saw that this feature is not considered at the moment by Atlassian - I mean opening a dialog when creating an issue from that screen.
My question is: is there any other way to workaround this? By tweaking some properties or scripting?
What happens when you try to create a child Issue in this manner?
I tried this on both Project types (Company-managed, Team-managed). I set a field to be "required", then pressed the "+" button on an Epic.
On both occasions it opened the full "Create Issue" dialog and let me create it there instead, so I could fill in the required field.
Is that not what is happening for you? If easier, please provide a screenshot of the behaviour you are experiencing!
Ste
Hi @Ste Wright
So basically I'm trying to create an issue from both the Issues and Roadmap screens.
In the first case the issue seems created, with a warning sign saying there is a problem in creation. After refresh, the task is gone.
In the Roadmap screen, it throws an error in the lower left corner and issue is not created as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How have you made the field required?
Did you make it required in the Field Configuration? Or did you add a Validator (or Rule, for Team Managed projects) to the workflow to make sure there was a value in the field when you create it?
If you are using a Company Managed project and made the field Required in the Field Configuration, then the dialog should pop open automatically.
If you made the field required through customization of the workflow, then you will encounter the problem you described.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill , yes, you guessed right, I'm using a validator for a transition in the workflow. It's this:
user.groups.includes("yourgroup") ? issue?.customfield_10001 != null : true
I needed to add this because there was no other way to make a field mandatory for a certain group of people.
Any ideas if this can be tweaked so the pop-up opens?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not that I know of natively. As far as I know, the only option is to remove the validator, or don't use those "quick create" buttons.
There's an open feature request and a bug which are related to this issue - vote for/watch:
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No worries!
Just to mention, there is a workaround using Automation - depending on whether the validator or the ability to use these quick-create options is preferred.
You could create a rule which...
It's probably not as a user friendly as a validator, but it's an option if of interest to you.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to great meetings, with less work. Automatically record, summarize, and share instant recaps of your meetings with Loom AI.
Learn moreOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.