Hi Mateus,
an Epic is meant to be a big long-running task. Epics come from the SCRUM methodology. Epics contain stories and last longer than one sprint. Stories should be ready within one sprint. But an epic is meant to be ready, someday.
A component is not a task. There is no Jira-issue for that (like it is for an Epic). A component is also some kind of container for issues, but it belongs to the project and therefore should be active as long as the project is alive. Their purpose is dividing your project into smaller parts. A component has no workflow, but a component lead. This is a user, who is responsible for issues belonging to that component. Just like the project lead for the project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Component/s you can set a specific assignee to each one, this is not a ticket but attached to a ticket like a label.
Epics are containers of stories.
Here is a good article for more information.
https://www.atlassian.com/agile/project-management/epics-stories-themes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.