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; } } }

Not mandatory field causes issues.

tifonas-katrina

Hi,

On bug I can request a HF(custom issue type).

When I click on approve a HF, from bug a clone is created with the same fields but with issue type HF.

For Bugs and HotFixes(custom issue type) the "Epic Link" field is not mandatory.

If "Epic Link" is not field, the HF is not created. Why is this happening? I have checked all transaction and epic link is not referred anywhere.

Regards,

Katerina

Accepted answers

Kyle Moseley

Are you sure the HF doesn't share a field configuration with the Epic issue type in your Field Configuration Scheme?

All comments

Kyle Moseley

Are you sure the HF doesn't share a field configuration with the Epic issue type in your Field Configuration Scheme?

tifonas-katrina

Hey Kyle,

Affirmative.

No shared config between HF and Epic

Kyle Moseley

I know you said you checked transitions, but are you 100% positive there is no 'Field Required' validator on any transition (including Create) for the new issuetype? Do Bug and HotFix share the same workflow?

tifonas-katrina

yeap

Welcome!

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

Quick Links

Find more posts tagged with

jira-software

jira-administration