Hello,
I share below several remarks, question about risk module of projeqtor.
Thanks in advancefor your feedback.
- The duplication of a risk proposes the creation of a “Problem” and not a “Risk”, normal or bug ?
- It would also be interesting to keep the initial type when we use a duplication
- Last topics, the notion of risk is effective with a notion of monitoring over a time frame, how to do this with projeqtor. can we follow the evolution of risks over a time frame?
Thanks
Regards,
Hello
- The duplication of a risk proposes the creation of a “Problem” and not of a “Risk”, normal or bug?
Yes indeed. There were two solutions. We chose this one.
And this, on the financial elements and the risks, because there is a logical sequence.
On other elements such as tickets, milestones, requirements or activities, the copy offers the same element.
- It would also be interesting to keep the initial type when using a duplication
It would indeed be possible to add an option. For the moment this is not planned in the roadmap. But ProjeQTOr offers on-demand development services. Do not hesitate to contact us.
- Last topics, the notion of risk is effective with a notion of follow-up over a period of time, how to do this with projector. can we follow the evolution of risks over time?
ProjeQtOr does not track risks over time. It would be an interesting idea, which however has never been requested so far.
So it's not planned in the roadmap but as for the copy option, you can propose the evolution.
Thank you for the feedback and the answers,
We have already contributed to the park management and the evolution of the token link to tickets, it is difficult to contribute more at the moment.
But add track risks over to the roadmap would be a good thing.
Have a good day and thanks again for your answers.