It would be good to be able to subscribe to the same "events" on the epic level that one can also subscribe to on the backlog level, e.g. "new epic created" etc.

by: Rene R. | over a year ago | Product Planning

Comments

• For sure! This seems like a big gap.

  by: Jeff C. | over a year ago

• Seems like a huge gap.

  by: Eugene K. | over a year ago

• YES!!! as a Product Manager, I spend a lot more time with the Epics than the User Stories. I would like to see a lot of similar behavior with the Epics that are available with the stories.

  by: Derek .. | over a year ago

• I came here to submit this as well.
  
  As an Epic Owner, I would like to be notified of any changes to Dependencies on the Epics I own. If some other work cannot be finished until an Epic I am responsible for is complete, I would like to be notified, as this could indicate a change in the priorities I communicate downstream.

  by: Daniel T. | over a year ago

• This is a huge gap for the teams I work with as well.
  
  Initially I was creating backlog stories that were copies of the epic so I could track them that way. This added a fair amount of manual effort to the process as I had to create separate projects for tracking the epics separate from the real backlog items.
  
  After abandoning this approach I've moved back to using the portfolio kanban, and manually sending messages to the correct people when an epic reaches a particular status. This only works if everyone working in the kanban knows the correct people to inform and when item reaches a certain level.
  
  Having basic status subscriptions for portfolio items would be a huge improvement to my teams workflows.

  by: Dave V. | over a year ago