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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • 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 best practices for linking Bugs and Epics?

I use Epics to group large bodies of work for a given release (includes stories, tasks, and critical bugs).

The team has started linking all bugs to Epics, which makes it harder/longer to close an Epic.

Do you link Epics to all bugs or just a certain priority?

After a release (ie, Settings page) , do you create a new Epic for that feature/release and group the work there? (ie, Settings page additions/improvements)?

3 answers

0 votes
Jack Community Leader Dec 30, 2019

This is really a subject topic. It comes down to whether you feel an Epic (product?) can be considered complete if bug exist. Keep in mind that when SW is involved bugs will always exists so at some point the Epic needs to close. The other question is will an epic consist of multiple releases of SW? In that case, for sure bugs should be part of the Epic. In most cases I would say that bugs should be linked to the stories that are part of the Epic and you could use "blocks" for bugs that block the Story from being consider releasable and "relates to" to those that don't block the release of the feature. You can then use JQL filters to know when a Story is complete. Ultimately, when you are ready to consider marking the Epic done you should consider moving any open linked stories out of the Epic maybe into a subsequent Epic.

0 votes
Joe Pitt Community Leader Dec 30, 2019

In my mind, bugs are in code so I would link them to the user story the code handles.  

0 votes

Absolutely, I would agree 100% to @Jack & @Joe Pitt 

Bugs are related to implementation details for a Story. Epics are representation of large blocks of Feature(s) in the Product. A epic/feature can be called complete with Bugs. Hence, we link Bugs to Stories

Suggest an answer

Log in or Sign up to answer

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