プロジェクト

全般

プロフィール

Vote #65322

未完了

Project WorkFlow

Admin Redmine さんが約2年前に追加. 約2年前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Issues workflow_41
対象バージョン:
-
開始日:
2009/06/05
期日:
進捗率:

0%

予定工数:
category_id:
41
version_id:
0
issue_org_id:
3450
author_id:
1867
assigned_to_id:
0
comments:
7
status_id:
1
tracker_id:
2
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

I know it could make the things a little bit complicated. So it could be placed as optional.
Some times projects can have status according to their stage or their conditions. Redmine has this feature for issues , what about create status or workflows for projects.
Eg:
Project A (alpha tests)
Project B (canceled)
Project C (delivered)
Project D (initiating)


journals

Felipe Campo wrote:
> I know it could make the things a little bit complicated. So it could be placed as optional.
> Some times projects can have status according to their stage or their conditions. Redmine has this feature for issues , what about create status or workflows for projects.
> Eg:
> Project A (alpha tests)
> Project B (canceled)
> Project C (delivered)
> Project D (initiating)

Creating a custom-field (List with project status) for project may help you.
--------------------------------------------------------------------------------
Enderson Maia wrote:
> Felipe Campo wrote:
> > I know it could make the things a little bit complicated. So it could be placed as optional.
> > Some times projects can have status according to their stage or their conditions. Redmine has this feature for issues , what about create status or workflows for projects.
> > Eg:
> > Project A (alpha tests)
> > Project B (canceled)
> > Project C (delivered)
> > Project D (initiating)
>
> Creating a custom-field (List with project status) for project may help you.

Right now Im doing that , I was thinking more in some kind of tipification of Projects
Something like
Type 1: Init -> Plan -> Build -> Deliver
Type 2: Init BackLog -> Iter -> Deliver -> Iter -> Deliv

--------------------------------------------------------------------------------
I think Redmine need a "Phase" tab on the project setting view.

The Phase's level is the top level in project, it's higher than the Version's level. When you create a version you must select a Phase where the version is belong to.
--------------------------------------------------------------------------------
J.N. Tang wrote:
> I think Redmine need a "Phase" tab on the project setting view.
>
> The Phase's level is the top level in project, it's higher than the Version's level. When you create a version you must select a Phase where the version is belong to.

What about a target version custom field, with this is posible to achive the phase feature and add other field like start date or risk level or what the imagination or the organizational context demands
--------------------------------------------------------------------------------
Felipe Campo wrote:
> J.N. Tang wrote:
> > I think Redmine need a "Phase" tab on the project setting view.
> >
> > The Phase's level is the top level in project, it's higher than the Version's level. When you create a version you must select a Phase where the version is belong to.
>
> What about a target version custom field, with this is posible to achive the phase feature and add other field like start date or risk level or what the imagination or the organizational context demands

I think the Phase is a character of a project, not of a version. There is a limit for a Phase, but no limit for version.
I think a phase tab is necessary.
--------------------------------------------------------------------------------
I agree with J.N. Tang (#5) on this - I see it the same way.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

Admin Redmine さんが約2年前に更新

  • カテゴリIssues workflow_41 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0