In Jira, Epics are containers for smaller units of work, which are often represented by other issue types like Story, Bug, and Task. Epics won't appear in the Backlog view in Jira, however they will appear in the sidebar. There are two tabs - "Versions" and "Epics". From this panel, you can view a list of Epics, expand an Epic to view details (number of ...
My initial thought is that Scrum is not appropriate for this situation, and something like Kanban is more appropriate. In cases where much of the work is BAU work that appears suddenly, you don't have the advantages of being able to plan a Sprint cadence and regularly deliver a set of value-adding work at the end. Low amounts of unplanned BAU work means that ...
JIRA boards are effectively views on to projects. That means it is possible to have many different boards containing the same data (or a subset of the same data).
For example, you could have a developer board, a UX board and a combined board all pointing at the same project. All JIRA needs is a way to work out which tasks to show on which boards. For ...
Kanban Isn't a Work Log
Kanban is a pull queue system that visualizes process gates and work state transitions. That means that each work item is pulled by the task performers from a previous queue when their WIP limits allow. Each board should represent a logical view of a single unified process. You can have multiple boards to queue work between ...
Some of the stories the designers work on feed directly into developer stories
Here is your problem.
Take a look at the INVEST mnemonic.
I - Independent - The PBI should be self-contained, in a way that there is no inherent dependency on another PBI.
You are taking a single story ("Make the alpha widjet fuzzy") and splitting it into two non-...
If the estimates are still there just that you do not see it on your view you need to check your Screen Scheme. If you are a Jira Admin you can check if the estimation field is there on the view in the "Configure Screen" admin section.
Re: components and epics, I think this will be a really good read for you.
The biggest takeaway there, and I think the biggest distinction between Components and Epics is that Components are timeless and categorical, whereas Epics are time-bounded bodies of work.
My Co-Founder created a detailed summary of all the possible options for linking Jira data with reports and charts in Confluence.
It includes some plugins (from Stiltsoft) that enable exactly what you're looking for.
Hope that helps!