跨越迭代的史诗 [英] Epics across iterations

问题描述

我想知道是否可以跨迭代使用Epics而不是每次都手动更新它们。



目前我们使用Back Log - >然而，当某些后退日志可以扩展多次迭代/释放时，这会导致问题。



所以我们尝试使用Epics - >返回日志 - >任务。 



例如，Epic可能是网站的一部分，例如管理。任何更改都会出现在该Epic下。 



我明白这不是敏捷方式，但某些任务/积压有时会扩展几次迭代。   
$


我希望Epic在默认级别改变时没有迭代限制，但确实如此（它从Epic列表中消失）。  
$


我正在尝试查看属于Epic的旧后台日志/任务，而无需手动更新每个积压/项目有点痛苦目前。 

I'm wondering if its possible to use Epics across iterations instead of manually updating them each time.

At the moment we use Back Log -> Tasks however this causes an issue when certain back logs may expand several iterations/releases.

So we tried using Epics -> Back Log -> Tasks. 

For example, an Epic may be a section of the web site, e.g. Administration. Any change would appear under that Epic. 

I understand that this isn't the agile way but certain tasks/backlog do expand several iterations sometimes.   

I was hoping the Epic wouldn't have the iteration limitation when the default level is changed but it does (it disappears from the Epic listing). 

I'm trying to get around viewing old back logs/tasks that fall under the Epic, without manually update each backlog/item its a bit of a pain at the moment. 

Micatio Software免费的IIS Azure Web日志应用程序

Micatio Software Free IIS Azure Web Log App

推荐答案

您好，

感谢您在此发布，

根据专家的说法，跨迭代不能使用Epics，需要手动更新。

As per the experts it is not possible to use Epics across iterations and it need to be updated manually.

问候，

这篇关于跨越迭代的史诗的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！