This question is locked. New answers and comments are not allowed.
Arjaan den Ouden
Top achievements
Rank 2
Rank 2
Arjaan den Ouden
asked on 02 Feb 2012, 10:30 AM
We use the Feedback Portal to communicate with our customers. To target the right feedback portal, the customer need to know how our internal projects are formed. That's not the desired way.
As a result, we receive feedback in our portals that should be addressed to another (internal) project. There is no way to relate feedback to another project.
I'd like to offer 1 portal to our customers where they can give their feedback and see our responses. I should be able to distribute feedback to the right project internally. Preferrable on a dashboard or something alike.
Kind regards,
Arjaan
As a result, we receive feedback in our portals that should be addressed to another (internal) project. There is no way to relate feedback to another project.
I'd like to offer 1 portal to our customers where they can give their feedback and see our responses. I should be able to distribute feedback to the right project internally. Preferrable on a dashboard or something alike.
Kind regards,
Arjaan
3 Answers, 1 is accepted
0
Hi Arjaan,
The portal work in that way because we want to provide the ability to associate stories and bugs with the feedback and this make sense only in the context of a project. It seems that hierarchy of projects will solve your issue because you will be able to have a portal on the root level. We thought for such functionality before and now we investigate and re-prioritize it.
At the moment I can suggest you to put all your internal project in one big TeamPulse project and build hierarchy of iterations or areas to differentiate them. Something like:
Projects
Project 1
Iteration 1
Iteration 2
Project 2
Iteration 1
Iteration 2
Jordan
the Telerik team
The portal work in that way because we want to provide the ability to associate stories and bugs with the feedback and this make sense only in the context of a project. It seems that hierarchy of projects will solve your issue because you will be able to have a portal on the root level. We thought for such functionality before and now we investigate and re-prioritize it.
At the moment I can suggest you to put all your internal project in one big TeamPulse project and build hierarchy of iterations or areas to differentiate them. Something like:
Projects
Project 1
Iteration 1
Iteration 2
Project 2
Iteration 1
Iteration 2
Regards,
Jordan
the Telerik team
New Cross Project Perspective in TeamPulse coming soon!
Want to know how TeamPulse could help you better track all your projects?
Want to know how TeamPulse could help you better track all your projects?
Reserve a seat for the TeamPulse R1 webinar today!
0
Arjaan den Ouden
Top achievements
Rank 2
Rank 2
answered on 06 Feb 2012, 12:18 PM
Hi Jordan,
Thanks for the reply. Please let me know when this functionality gets scheduled.
For the meantime, I'll make one big project. Is there a way to manipulate my database that alle projects are moved into one?
Regards,
Arjaan
Thanks for the reply. Please let me know when this functionality gets scheduled.
For the meantime, I'll make one big project. Is there a way to manipulate my database that alle projects are moved into one?
Regards,
Arjaan
0
Hello Arjaan,
Elena Peneva
the Telerik team
I am sorry but we cannot provide you with a solution for merging your existing projects into one. Most of the settings including the basic ones such as items' statuses are done on per project level and we have no mechanism for merging them. We have the same concern for feedback items and that's why we do not allow projects migrations.
However, we will think about your case and if we find a future solution we will let you know.
Elena Peneva
the Telerik team
New Cross Project Perspective in TeamPulse coming soon!
Want to know how TeamPulse could help you better track all your projects?
Want to know how TeamPulse could help you better track all your projects?
Reserve a seat for the TeamPulse R1 webinar today!