Epics should not be assigned to sprint but stories should be assigned

[Vinay_Aggarwal]

Hi All,

We are facing a strange problem. Someone keeps updating sprint # field in Jira against EPICS  which is causing following problems.

1. As we all know, at the time of starting sprint, JIRA records total of all story points as team commitment. This is based on all the cards assigned to sprint. Now, in our case, since epics also being assigned to sprint, estimate of epic also getting added to team commitment which gives wrong picture of team commitment. In other words, if team commits to do work of say 50 points in a sprint, JIRA shows team commitment as something 200, 250 or so because it counts points given to epics as well.
   
   
2. These epics start appearing on team’s daily sprint board which is annoyance as team want to see what they are working on which are stories, tasks, bugs etc. Epic is not workable or actionable item for them but they end up seeing epic as well every day whenever they refer sprint board. This is unnecessary.

How to solve this? As per me, Epics should not be assigned to sprint. What do you say?

[Bill Sheboy · Accepted solution]

Hi @Vinay_Aggarwal   Welcome to the community!

The behavior of adding epics to sprints is apparently considered an open defect.  Here is the link if you want to review/comment on it:

https://jira.atlassian.com/browse/JSWCLOUD-11130

Best regards,

Bill

[Vinay_Aggarwal]

Appreciate your reply.  Is there any other official stuff (e.g. documented best practice or something) which I can show to my stakeholders to convince them it is indeed bad practices to assign epic to a sprint? Thanks again.