Feature #23858

Add another version status 'planed'

Added by Robert Schneider about 3 years ago. Updated about 3 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues planning
Target version:-
Resolution:

Description

As described in #23855-2 I'd like to have another version status that could be named 'planed' or 'prepared' or whatever. This status could be used before a version gets concrete and in order to collect issues when the version is still rather variable. On the roadmap such versions would be hidden by default like the Completed versions.

For the redmine project it might be also helpful so that versions Candidate for next major release, Candidate for next minor release and Unplanned gets hidden on the roadmap, though they are still accissble.


Related issues

Related to Redmine - Feature #21577: The version should get a status archived like projects New

History

#1 Updated by Robert Schneider about 3 years ago

When I think about it... Maybe 'private' versions would be interesting as well...

Update of my comment: Would be to complicated, I think. Forget this.

#2 Updated by Marius BALTEANU about 3 years ago

Robert Schneider wrote:

When I think about it... Maybe 'private' versions would be interesting as well...

Or maybe 'backlog', a term that is used very often in agile development.

#3 Updated by Wim DePreter about 3 years ago

Related to #21577

#4 Updated by Robert Schneider about 3 years ago

Hm... In my opinion 'backlog' would be something different. A version named 'backlog' would be a pseudo-version (probably like the three mentioned special versions in the Redmine project). I would see 'planned' or 'prepared' more related to a version. Even if it is not a version of a piece of software. For me a version has or will get a date (release date, completion date,...). But a backlog is just a collection of tickets without a certain point in time.

Those three Redmine pseudo-versions are not resolved when this feature would be implemented. It would be just a nice side effect that they can be hidden this way. But that wasn't the main purpose of this request. I mainly wished to have something so I can separate new, variable versions (which are not so relevant for others) from those that are more concrete (but are not locked).

But having something like a backlog would be also useful, I guess. There are probably already some tickets about this idea.

#5 Updated by Olivier Houdas about 3 years ago

Did you try using Version custom fields for that?
You can filter on Version's custom fields, and it could let you see the issues you're looking for.
On our side, we have created a Current target boolean field, and based developers' queries on this field, so that their default filter can always show bugs assigned for the next version, and they do not need to update their query when the version is built.

#6 Updated by Robert Schneider about 3 years ago

I see. But I'd prefer the 'planned' status so that also the Roadmap can be 'cleared' from unstable versions in future.

#7 Updated by Toshi MARUYAMA about 3 years ago

  • Related to Feature #21577: The version should get a status archived like projects added

Also available in: Atom PDF