Documentation #241

simplify redmine workflow

Added by wuttke over 7 years ago. Updated about 7 years ago.

Status:ArchivedStart date:23 Mar 2013
Priority:NormalDue date:
Assignee:herck% Done:

0%

Category:-
Target version:Sprint 13

Description

It must be possible at any moment to mark an issue as rejected or resolved or "in progress".

The workflow described by Walter (now at http://apps.jcns.fz-juelich.de/doku/sc/intern:redmine) is convincing as a default and as a convention, but it must not be so hard wired that non-standard actions require ugly workarounds (like setting an issue to backlog then sprint only to close it).

History

#1 Updated by herck about 7 years ago

  • Status changed from New to Backlog
  • Target version set to Sprint 13

#2 Updated by herck about 7 years ago

  • Status changed from Backlog to Sprint

#3 Updated by herck about 7 years ago

  • Status changed from Sprint to Resolved
  • Assignee set to herck

The possible workflow rules have been loosened a bit now. If further restrictions should be removed, please contact me.
However, putting issues to "in progress" should only be possible for Support and Documentation items; all other trackers are by definition in progress if they are assigned to someone and attached to the current sprint and not resolved/closed. I also think that sprint items should never be directly put to "close", but that we do this in one shot at the end of the sprint, so that everyone has at least an opportunity to comment/review/...

#4 Updated by herck about 7 years ago

  • Status changed from Resolved to Archived

Also available in: Atom PDF