What you need
Folder 1 | Folder 2 | Folder 3
project proposal: created | submitted | checked | postponed | rejected | accepted
With the project application you can ensure that only those projects are processed that you have actually approved. To keep the process as flexible as possible, you will find suggestions on how to map a project proposal in smenso Cloud here.
Create project proposal
There are different possibilities to map project proposals in smenso Cloud.
- Create a task with the name [Project Proposal]
- Create a project and map the project ideas via labels and flavors
- About general release workflow using flavor
It depends on how complex you want to make the application process. Take a look at the different options below:
Project application via name
Project application via label
Project proposal on flavor (with process)
Via release workflow
As already shown with the project idea, you can use a flavor "Workflow: Release" to have the idea released. In combination with the label "Project proposal" you can filter all project proposals in the portfolio at any time and monitor the approval workflow. Have a look at the article.
Release or reject project application
If the project proposal is approved, the project can start "properly". It is best to structure the folders in the project portfolio by phase. Then you can move the project one phase further after it has been released. Of course you can always write in the comments why you have approved or rejected something.
If the project application was mapped via labels, the label will be removed again. If it was created as a flavor, the status is set to "released" and remains the same. Alternatively, the flavor can be deleted again.
The project feed does not cause any status to be lost, and the project or project proposal is retained for later. In this way, you can always determine how the project proposal was released (by whom and when) or not.