You can set up Jira to reflect how your team works or to influence how it works. Here's what I mean. When a team starts to use Jira, the first instinct is to configure it to match the processes and methods and language of how the team currently works. This makes sense because you want your team to go into Jira, especially early on in your use, and see something familiar. Issue types named for real work people do and workflow steps that reflect how actual work gets done on your team and field names that reflect names of things your team recognizes.
Getting Confluence and Jira talking to each other brings many benefits to business leaders, not just developers