Reassign owner of an issue (Feature #358)

+1 on this feature. We have been using the change author plugin in RM, and ultimately rolled our own, to allow for this. Great to see that it is being rolled into the product. Keep up the great work.

Sorry, that this feedback is coming so late. I should have thought about it earlier. I think this is a nice feature and there is definitely a use case for it - we have been asked to implement something similar (although we didn't do it yet).

I have had a quick look on your pull request and I think it adds a whole lot of complexity. It has to, I guess, but I think, it should be possible to get something similar with less effort and a much broader use case.

I think, the same could be achieved by:

1. Allowing the author to unwatch issues. This was discussed before and I think there was some general agreement, that it would be relatively easy to implement and we would get rid of some special case handling, if the author was just one of the watchers. I think, forum post currently work that way.

2. Implementing foreign key based custom fields. This way would could not only have a enterer (??) and author, but also a manager, an accountant and what not.

With these 2 ingredients, we could configure something that works just like your pull request but is applicable for even more use cases. Additionally we would hopefully remove complexity (at least in part 1) instead of adding it.

I hope this sounds like useful idea dropping and not like bashing your work and effort.

What do you think?

Gregor Schmidt wrote:

I have had a quick look on your pull request and I think it adds a whole lot of complexity. It has to, I guess, but I think, it should be possible to get something similar with less effort and a much broader use case.

I agree, it's a bit complex which I why I wanted some reviews. Part of that is because this code is really old and was before some of my other refactorings.

With these 2 ingredients, we could configure something that works just like your pull request but is applicable for even more use cases. Additionally we would hopefully remove complexity (at least in part 1) instead of adding it.

Both of your ideas would be good features but I don't think they could replace this one. There is a lot of code and other things that are only looking at the author. Having to pull in custom fields would make things even more complex.

From a plugin developer API perspective: I'd like to easily get the author of an issue, without having to check if "Author custom field" is set and valid.

I hope this sounds like useful idea dropping and not like bashing your work and effort.

Not at all. I'd rather get some feedback and discuss the code under review to make sure it's good enough before we commit to using it.

Another question: what part(s) of the code make it seem complex to you?

I realy need this feature. How can I help with integrating this feature in production ChiliProject?
Unfortunalty I haven't know ChiliProject very well yet, that is why I can't give you any valuable feedback about your patchs.

I haven't completely followed the discussion through, but what's the status on this? Ready for review pending a rebase, or is there still more to be discussed?

Needs to be rebased and will probably have to wait until 4.0. I've been getting some feedback on it from a few of my customers who are already running it.

Excuse me, but what do you meen by 4.0?

I am waiting for this feature eagerly.

Yuriy Cherniavsky wrote:

Excuse me, but what do you meen by 4.0?

Version 4.0, the next major release after the one we are finishing up.