JIRA: v8.5.3#805003-sha1:b4933e0
ScriptRunner: 5.7.1.1-p5
Hi, we have the following setup:
- two development teams, each having their own board
- both teams have their own sprint
- they work on the same codebase and therefore share the same JIRA projects
- when planning sprints, a predefined package of issues is divided across the two teams using two labels, Team_A and Team_B
- the boards' filters are configured so that only issues from the respective team (having the respective team label) show up
- both teams prioritize and discuss their issues and start their sprint independently
- sometimes a running sprint has to catch up with real life: issues are removed from a running sprint in exchange for other issues - this may be a new issue that wasn't in the predefined package before - or issues are thrown "over the fence" to the other team
We have a set of homebrew tools that evaluate sprints, draw burnups and give us insights. For some of these tools, it is necessary to find issues that were removed from a sprint.
The removedAfterSprintStart issueFunction comes in handy, but it has a limitation that looks like a bug to me: It does only report issues that were removed from the sprint but still match the board filter. For us, this means a removed issue is only found if it still has the respective team label, which is a severe limitation for us.
I propose and ask to remove this limitation from the removedAfterSprintStart issue function. In case anyone wants to filter issues that still match the board filter, this condition can be explicitly included by:
issueFunction in removedAfterSprintStart(..) AND filter = [id of baord filter]
Thanks in advance for any insights to this issue.
