If they want to code, let them code. Facilitate it so they can spend more time coding.
If they're qualified, they know how to use Jenkins and Jira, when to script and whether to automate. If you start regulating Jira with excessive rules (classifying as epic or story, team, feature, sprint, component, DOD, estimate, only work from top of backlog, etc.) then a dev is is really going to be disincentivised from using it.
Whether or not they know how to use JIRA only tells you whether or not they've used JIRA, not whether or not they're qualified.
And in my experience, most developers (myself included) will just not use those tools if they're not required to. And if you have no idea what level of information you're going to get from an epic, story, bug, task, or subtask until you know who wrote it, the tool is largely worthless.
If they're qualified, they know how to use Jenkins and Jira, when to script and whether to automate. If you start regulating Jira with excessive rules (classifying as epic or story, team, feature, sprint, component, DOD, estimate, only work from top of backlog, etc.) then a dev is is really going to be disincentivised from using it.