It will be more convinient, in my opinion, to distinguish projects as active and inactive.

Registered by Nikolay Musatov on 2012-05-07

It will be more convinient, in my opinion, to distinguish projects as active and inactive.
As for me, it is convinient to use projects to account the cost of short-term events, like business-trips, e.t.c.
Due to the id-reference relation "transaction-project" one shouldn't delete project after the end of event.
Also, it is inconvinient to dig in long projects list while new transation is creating.
Due do this, I suggest additional attribute of Project entity - boolean "isActive".
Request Code Reviev.

Blueprint information

Status:
Not started
Approver:
Denis Solonenko
Priority:
Undefined
Drafter:
Nikolay Musatov
Direction:
Needs approval
Assignee:
Nikolay Musatov
Definition:
Review
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.