What are good approaches to test a sprint task (e.g. greenhopper dashboard) after it's been completed?

[David Parks]

Some tasks from the sprint need to be tested, a new piece of code/functionality for example, and some don't, document some feature for example.

What are some typical ways to model this workflow? After a task is done we want someone to follow up and test that (where appropriate).

If I add a workflow transition to "In Testing" and put it back in the "To Do" column of the task board we won't be able to easily track/credit who did the original work on that task (or so it seems when I think about it).

So then I wonder if I should try to create some kind of workflow process that creates a new "Testing" task, but then I'd lose all the comments on the original issue that might be valuable.

Is there some other process that is typical that I'm not thinking of? What do *you* do?

[Renjith Pillai]

What we do for such cases was indeed create a new task (as per the case, different issue-types) and simple link to the original backlog item. Whoever works on it gets a clear linkage to the original item and all comments and data is available there.

[Lukas Med]

Thank you for your reply but this answer is not correct because I must input "5/Zář/18" and if I select the day in calendar system input automatically "5/IX/18" after click on button system write that this input from calendar is incorrect. I think that issue is between Czech and English format and language of system. We are using Czech language in Jira.

Thank you for additional information. Lukas.