None, unless you configure something.
Jira is an "issue tracker", and it comes with a sample range of "issue types" off-the-shelf. Functionally, there is no difference between them. BUT, most of the configuration for a project is hung off the issue type, so you can have different screens, fields and workflows for different issue types.
So, really, the difference is not much more than "the issue types have different names". In English terms, a feature is usually "something new we'd like" and an issue is "a really wide ranging word that means something needs doing, but it's not covered by the other issue types". But you can configure whatever you need!
(Note, there's an exception here if you whack in the Agile plugin - that makes some baseline assumptions about stories and epics, but you can still change that if you want)
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs