An Epic is an issue that you link with stories, tasks and other issue types as you need to group them together.
A component is a part of a project, and the component list is used to indicate what component(s) an issue might belong to in that project.
So I'm not sure what you mean by "epic used by other components"?
Okay. Maybe, I'm a little bit confused of what components can do. Components are used to group issues into smaller parts. From this, I assume components set boundaries to issues. If we have no permission to one component, we should have no idea about issues inside it. Right now, I'm trying to plan our JIRA Setup. We have at least 3 issue types: Epic, Task and Subtask. From this, I want Epic to be useful for all components but Task/Subtask should only be used within a component. Will this be possible?
Ok, you're using the word "components" in it's generic form, but in JIRA, it has a specific meaning for a type of field which is not the same level as what you're talking about.
It's not quite this simple, but in JIRA there's a hierarchy:
Then you have the concepts:
From your explanation, I think what you are calling "components" would be best represented by projects in JIRA, because users can be added to projects to give them visibility of the issues, and it's a logical group of issues. Your issue types don't really matter, you can put whatever issue types you want in each project. Except for Epics - yes, they can go across projects.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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