[
https://issues.jboss.org/browse/JBIDE-19424?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-19424:
---------------------------------------------
no :)
the intent is that ds_maint returns all issues for the maintanence stream (including
closed)
similar to that ds_master shows all in master stream (including closed).
They are meant to be used as building block for more specific filters.
i.e. "ds_my_next_maint_unresolved" shows the unresolved in the next maintanence
that you are assigned or component owner of.
Maybe there is some specific filter you want created ?
jiralint's ds_maint filter doesn't differentiate between JBDS
8.0.x (completed) and 8.1.0 (in progress/upcoming)
----------------------------------------------------------------------------------------------------------------
Key: JBIDE-19424
URL:
https://issues.jboss.org/browse/JBIDE-19424
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.2.3.Beta1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
In querying for all the open issues for 8.1.0 / 4.2.3, the ds_maint filter also returns
all the 8.0 stuff, which are all closed.
Thus, to see all the Requirements for JBDS 8.1, we need this:
https://issues.jboss.org/issues/?jql=filter%3Dds_maint%20and%20component%...
(10 issues)
instead of this:
https://issues.jboss.org/issues/?jql=filter%3Dds_maint%20and%20component%...
(45 issues)
Should ds_maint know that it's just 4.2.3/8.1.0, without having to subfilter?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)