Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

What are the pros and cons of managing a business project using an EPIC vs using a PROJECT in JIRA? Edited

Hayder L I'm New Here Feb 08, 2021

Hi,

JIRA has been set up such that a JIRA project corresponds to a department. At the same time, we are looking to use JIRA for traditional project management and our bread and butter consists of client software projects.

Could anyone advise on the pros/cons of the usage of Epic vs Project in JIRA to manage a software project? Particularly relating access control (e.g. only project team members should be able to view project contents/tasks; project reporting in terms of milestones, resource management)

Thanks!

1 answer

Hi @Hayder L,

Epic is an Issue Type within a Project, which means Epic can only have 1 workflow, 1 screen scheme, 1 field configuration and etc.

Let's say, for example, you have Epic A and Epic B and you want them to have a different set of fields or workflow or statuses, that's not possible by default.

You can make a bunch of automation and/or use third-party apps to somehow get you there. This would also lead to more maintenance work in the future when you have a bunch of workarounds and hack around the product design.

For Project, well, you can have few Issue Types and they can be tied to almost all the schemes individually, which means each Issue Types can have a unique set of fields, field configuration, workflow, and etc.

Back to your question:

Could anyone advise on the pros/cons of the usage of Epic vs Project in JIRA to manage a software project? Particularly relating access control (e.g. only project team members should be able to view project contents/tasks; project reporting in terms of milestones, resource management)

Actually for this, if you already have an existing project that you would like to use, I will recommend adding a new Issue Type called "Access Control". You can use Issue Security Level if you want to separate the view permission of this Issue Type to others within the project.

Epic issue type is actually for some sort of categorization of a few stories. This is more to the software development methodology, where you have a parent task and then you break down it into smaller stories.

I hope that helps.

Thanks,
Moga

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,121 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you