Moving issues to another project works but it copies the issue instead of moving it. It is also marked as fixed in the original project, which is confusing.

Submitted by Danny Groenewegen on 10 March 2010 at 10:59

On 10 March 2010 at 11:29 Sander Vermolen commented:

I prefer not to have destructive updates in YellowGrass. Furthermore, when issues are moved instead of copied, external references may break and issue numbering may get confusing. I agree marking moved issues as closed may be confusing. In future, this can probably be solved by annotating the issue with a resolution strategy (issue 39). For now, I will add a comment on move indicating the issue has been moved.

On 16 March 2010 at 12:57 Sander Vermolen commented:

Issue fixed in new yellowgrass version. When a comment is moved to another project, the current issue receives a comment from yellowgrass, saying it has been moved and to which project. It also contains a reference to the new issue. The original issue is still closed as not to make destructive updates.

On 12 May 2010 at 15:07 Lennart Kats commented:

How about a little arrow icon instead of the check mark?

On 12 May 2010 at 15:57 Sander Vermolen commented:

In the next release, issues have a log which registers all issue events. Moving an issue is one such event. Events are presented on the issue page. Such presentation should already be much clearer than just a comment. Indeed, changing the tick to be an arrow should improve usability further. I have reopened this issue and assigned it to the upcoming release.

On 16 December 2010 at 14:19 Sander Vermolen closed this issue.

On 16 December 2010 at 14:19 Sander Vermolen commented:

Added registration of issue moves in the issue log. Registration includes a link to moved issue. New feature available in release 1.00.

Log in to post comments