How do I set a Bug field as required or optional?

[FiRa Administration]

I'm setting up a list of custom fields for Bugs. Users consistently miss filling out important fields in these Bugs, so I'd like to set some of these fields as required prior to submitting the bug. Is there a way to do that? I've looked through the Custom Fields documentation, but either I'm missing something or this is something basic that isn't implemented. 

[Dave Liao · Accepted solution]

@FiRa Administration - this resource on specifying field behavior will be your friend!

You'll want to adjust an existing field configuration to get this done, or create a new one (depending on your exact business requirements).

[FiRa Administration]

Hey Dan,

Thanks for getting back to me. Before submitting this question, I created a new field configuration and assigned it to the required Screens (I think). Still, the new field (Specification) isn't appearing in the list of fields for Bugs. I'm not sure where the gap in behavior is here. Basically here's what I need to happen:

1. User creates a new Bug via the Backlog
2. As part of this Bug, the "Specification" field needs to be filled out
3. If the "Specification" field isn't filled out, then an error is thrown at the user

Despite following the steps in that link you provided (both before submitting the question and after), I'm not seeing the new "Specification" field, just the old one I created from the Bug view. Here's what I'm seeing:
I'm not sure if I'm just mixing up terminology, or what. 

Does this help explain what I'm trying to get at?

Thanks,

Aaron

[Dave Liao]

@FiRa Administration - hi Aaron! You'll want to ensure the custom field "Specification" is added to any screens your project uses, or issue layouts (if you're using the new Jira issue view):

https://confluence.atlassian.com/adminjiracloud/defining-a-screen-776636475.html

Hope that helps!

[Dave Liao]

@FiRa Administration - ha, just realized your computer/mobile autocorrected my name from Dave to Dan 😉

[FiRa Administration]

Hi @Dave Liao - oops! Sorry about that. 

I'm pretty sure I have it assigned to the screens used in our project, but I'll check in on the issue layout. That sounds like something I haven't looked at.

- Aaron

[Dave Liao]

@FiRa Administration - ha, no worries!

• If you're using the new issue view, you need to look at the issue layout.
• If you're not (and you're using the legacy view), you only need to be concerned with screens associated with your projects.

[FiRa Administration]

@Dave Liao - Ah, yeah, this is where I'm running into the problem, I think. I have the field configured via the first link you sent, and I think that I have the field applied to the appropriate screens and whatnot, but when I have the issue layout pulled up, it's not there. The only thing that does appear is the old version of "Specifications" that I had previously created, which does not have the ability to be marked as Required/Optional. Here's what I'm looking at: 

Any ideas are welcome! 

[FiRa Administration]

@Dave Liao - Hi Dave, after playing around with my project and setting up some others, I'm starting to get the suspicion that I'm running into these problems because the project I'm using is a next-generation project. Does that make sense? If so, is there a workaround you're aware of?

[Dave Liao]

@FiRa Administration - ahhh, gotcha! Makes sense.

Next Gen projects don't yet support required fields and there's no workaround that I'm aware of. It seems like others also have the same need as yourself.

I would vote up JSWCLOUD-17392 if you want this feature - I just voted it up!

[FiRa Administration]

@Dave Liao Thanks for pointing me to that. I voted up the request, as well. Thanks a lot for sticking with me on this!

[Dave Liao]

@FiRa Administration - no problem! I'm too ashamed that next gen projects still don't have required fields available, so it's fine if you don't mark my answer as an accepted answer 😂

[FiRa Administration]

@Dave Liao  - Rest assured, I hadn't marked it as accepted because I missed the button to do so! Still new to this platform. Anyway, I'll keep tabs on that thread and chime in if it might help.