"Rejected" issues

Added by Benjamin Neau over 11 years ago

Hi,

On my company's redmine bug tracker, we have introduced an issue state named "Rejected" for issues which are rejected e.g. when a issue is already covered by another issue.

Of course, we do not want issues with a "Rejected" state to appear as Open, for they are closed; but on the other hand, we do not want them to appear on the version's roadmap page either (which we would like to use as a basis for our change log, with as little changes as necessary).

Would it be possible to conciliate both our requirements?

Or maybe we are not using Redmine properly, in which case we'd be eager to know how to proceed in another fashion to fulfil the aforementionned requirements.

Thanks for your time and consideration.

Best regards,
Ben

Replies (2)

RE: "Rejected" issues - Added by Mischa The Evil over 11 years ago

Benjamin Neau wrote:

(...)

Of course, we do not want issues with a "Rejected" state to appear as Open, for they are closed; but on the other hand, we do not want them to appear on the version's roadmap page either (which we would like to use as a basis for our change log, with as little changes as necessary).

Would it be possible to conciliate both our requirements?

(...)

Have you seen RedmineIssueTrackingSetup in the Wiki? You can set the "state" (thus open/closed) for each individual issue-status. So you can set the closed-state for your status "rejected".

Quote from the Redmine Guide:

Each status has the following two configurable options:
  • Closed: indicates that the issue is considered as closed (more than one status can be declared as closed)

This is also how I personally used the "rejected" "issue-state" in my own Redmine. This worked (and still works) pretty well for me... YMMV :)

 
Kind regards,

Mischa.

RE: "Rejected" issues - Added by Benjamin Neau over 11 years ago

Hi Mischa,

First and foremost, thanks for your time and help on this issue!

Mischa The Evil wrote:

Have you seen RedmineIssueTrackingSetup in the Wiki? You can set the "state" (thus open/closed) for each individual issue-status. So you can set the closed-state for your status "rejected".

Quote from the Redmine Guide:

Each status has the following two configurable options:
  • Closed: indicates that the issue is considered as closed (more than one status can be declared as closed)

This is also how I personally used the "rejected" "issue-state" in my own Redmine. This worked (and still works) pretty well for me... YMMV :)

Here too, the "rejected" state for issues is currently defined as closed. Our problem is that when we go to a given version roadmap page1, the "rejected" issues are appearing, striked out, just like any other closed issue (like resolved ones) while we do not want these "rejected issues" to be shown.

The closest thing to a solution we've come up with ATM is to define a dedicated "ChangeLog" cross-projects issues-viewing screen, which would only display the issue tracker and subject for all issues but the ones with a "rejected" status; grouped by target version.

[1] I read on the page you linked that there is a changelog feature too, but I was unable to find it, or even the "Issues displayed on changelog" option on any of our issue trackers. We use the 0.9.3 version of Redmine.

Best regards,
Ben

(1-2/2)