Apparently the "Create issue" feature does not care about configured create screens or hidden fields, and just tries to tank them in there.
I have a project which does not use "Component/s", "Affects Version/s", "Fix Version/s", "Original Estimate" and "Priority".
Trying to create an issue in this project basically gives me an exception telling me that I HAVE to have those.
Can this really be right? I would expect lot's of people remove a couple of these fields to clean things up.
It's version 3.0.10 of the plugin, and it would amaze me if, after 3 major versions, custom field configurations are unsupported.
I'm not that familiar with the connector, but check the UI - does the project demand these fields when you try them directly? If it does, then you need to amend your field configuration to make them optional. (I suspect this is what's happening, but I can't be sure if the connector is also demanding the fields irrespective of Jira config)
Every team in the world is unique, and so Atlassian believes that each and every team's best way of working needs to be molded to their unique circumstances – ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot