Unable to retarget support request

Who has the right to transfer a question to another project? Anyone, Admin? I'm inclined to set this barrier low, and raise it only if it proves to be a problem.

I agree. I think any logged in user should be able to do it.

The feature is roughly in place in my branch. I used the ProjectScopeWidget with the DistrobutionOrProduct vocabulary.

I think we want a DistributionOrProductOrSourcepackage vocabulary. Including Projects complicates the act of transfering a question to another target. I think that Answer Contacts are savvy enough to know how to select the Product directly.

The ProjectScopeWidget should be replaced with a widget that guarantees a valid QuestionTarget is provided. I can base the widget on ProjectScopeWidget or FileBugTargetWidget. I don't care for the choose the target type approach of the latter widget, but it matches out targeting need very well--no new vocabulary is needed.

It could be argued that the main use case for retargeting is that the major target (product or distro) is wrong. The 'Edit question' action already allows somebody to change the source package of the question. If we simply add another 'target' field to that form, it would be possible to retarget to another source package in another distribution using two operations on that form. So the ProjectScopeWidget with DistributionOrProduct vocabulary is probably enough.

On Wed, 2007-04-11 at 14:19 +0000, Francis J. Lacoste wrote:
> It could be argued that the main use case for retargeting is that the
> major target (product or distro) is wrong. The 'Edit question' action
> already allows somebody to change the source package of the question. If
> we simply add another 'target' field to that form, it would be possible
> to retarget to another source package in another distribution using two
> operations on that form. So the ProjectScopeWidget with
> DistributionOrProduct vocabulary is probably enough.

I'll play with that.

--

__C U R T I S C. H O V E Y_______
Guilty of stealing everything I am.

Fixed in RF 4153.

Fixed released on 2007-04-30 in version 4080.