JIRA JQL：当前冲刺中解决的问题 [英] JIRA JQL: Issues resolved in the current sprint

问题描述

我希望能够过滤当前sprint中已解决的问题。通常，这将用于防止在先前的sprint中解决但在测试中延迟（未重新打开）的问题，这些问题在我们讨论开发人员实现此sprint的结果时出现。

I would like to be able to filter for issues that are have been resolved in the current sprint. Generally this would be used to prevent issues resolved in a previous sprint but delayed in testing (not reopened) showing up when we are discussing what developers achieved this sprint.

已解决的问题应该也会出现，但它们不是问题，就好像它们在上一个sprint中关闭时一样，它们也无论如何都不会进入。

Closed issues should also appear, but they are not a problem, as if they were closed last sprint, they wouldn't roll over into this one anyway.

在模拟JQL中，它将是这样的：

In mock-JQL, it would go something like this:

project = "Project name" AND status in (resolved, closed) AND statusChanged() > startOfWeek() 

我见过 startofweek（）和朋友，但不是 startofsprint（）之类的东西。

I have seen startofweek() and friends, but not something like startofsprint().

我们有JIRA OnDemand，因此我们无法安装本地Java附加组件。

We have JIRA OnDemand, so we can't install local Java add-ons.

任何方式获得此信息？

推荐答案

一种针对最新sprint中已解决的问题创建查询的方法是为其创建过滤器。
然后，您可以在所有需要在该主过滤器的子集上工作的不同JQL中重用该过滤器。
警告这种方式的劳动强度很小-如果要使用多个过滤器，它会击败其他替代方法。

One way to create queries on issues that are resolved in latest sprint, is to create a filter for them. Then you could reuse that filter in different JQLs that all need to work on subsets of that master filter. Warning This way is little labor intensive -- nevertheless it beats other alternatives, in case you are working with multiple filters.

1. 为最近的冲刺结束问题创建并保存过滤器

1. Create and save filter for "Closed in latest sprint" issues

status changed to (Resolved, Closed) after 2014-09-15

在其他JQL中，该过滤器可以重用

In other JQL-s reuse that filter

// First JQL reusing filter
project = "My Project" and status in (Resolved, Closed) and filter = "Closed in latest sprint"
// another JQL reusing filter
project = "Other Project" and assignee = currentUser() and filter = "Closed in latest sprint"

无论何时开始新的冲刺，都记得在最近的冲刺中关闭过滤器中更新日期

确实，如前所述，这是一种手动且耗时的方法。但是，如果您处于OnDemand模式，因此无法添加自己的JQL函数，该函数将在定义的Rapidboard中返回最新sprint的开始日期，那么您很不走运。

Indeed, as said previously, this is somewhat manual and time consuming way. But if you are in OnDemand and therefore cannot add your own JQL function that would return start date of latest sprint in defined rapidboard, then you are pretty much out of luck.

这篇关于JIRA JQL：当前冲刺中解决的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！