[SOLVED] Copy requirement as new project?

Hi,

All our projects come from business requirements. Sometimes requirements are cancelled but when they become a real project, it would be good to be able to copy requirement as new project because it's dull and repetitive to copy name, description, estimated work, etc…

So why can't we copy requirement (or any other element) as a new project?

Thank you,

Sorry, I clicked on Solved by mistake.

Here is how we work:
We have big projects:
1. MY PROJECT

We have sub projects:
1.1 REQUEST FOR CHANGE 1
1.2 REQUEST FOR CHANGE 2

- Each request (change or fix) come from our customers and is about ONE requirement. Example: change the color of the button.
- For this single request, we will have everything, from prestudy, to business requirements, to specs, to developments, to tests, to UAT and to deployment, etc.
- When the requirement is in prestudy, we study the feasibility and if or not it will become a real project, if we will cancel it or do it later when we have the budget. At this state, the requirement is a requirement, not a project (yet).
- When we validate the requirement, it becomes a single project (from specs to deployment).
- We have two workflows in parallel: a financial workflow (statuses quotation, contract, order, etc, to know at which state we are) for the requirement, and a project workflow (statuses prestudy, specs, etc) for the project.

So requirements and projects are linked as 1:1 in UML. I checked with projects manager, it will always be like that (except when initiating a new big project, which should be rare).

Thank you,

Yes, our suppliers invoice every little changes we ask them so it's a whole project. And I can't change the way they/we work as I have no influence on it.

Among other reasons, a Change Order is linked to every financial elements such as the Quotation, Order, Invoice, etc and we can't link and filter activities as easily and as intuitive as with projects.

Isn't adding Project to Copyable table a better way to solve this issue?