Branch / Trunk testing

General discussion of Mantis.

Moderators: Developer, Contributor

Post Reply
Reinder
Posts: 119
Joined: 26 Apr 2005, 11:08

Branch / Trunk testing

Post by Reinder »

Hi all,

I have a problem as follows; At the moment we are using SCRUM as a development proces which works fine. With this, every story (feature) is first created in a brach and if deemed good enough by QA, migrated to the trunk.

The trunk will only consist of migrated stories and (direct) bugfixes. So every issue found in the branch will be solved and tested there.

So far, so good. However, Qa also likes to retest the issue in the trunk because of regression that might occur. This would mean we should not close the issue when tested in the branch, but somehow indicate it is tested in the branch and still needs to be tested in the trunk.

I dont want to create a seperate status for this (since issues can also be found in the trunk). The current flow is:

New->open->assigned->resolved->to bet tested-> closed (happy flow)

Anyone encountered the same problem and can help me with a solution?
atrol
Site Admin
Posts: 8366
Joined: 26 Mar 2008, 21:37
Location: Germany

Re: Branch / Trunk testing

Post by atrol »

Maybe you want to use the field "Resolution" for it?
Don't set it to "Fixed" before QA has checked it in trunk.
Please use Search before posting and read the Manual
Post Reply