Preventing status collisions

Get help from other users here.

Moderators: Developer, Contributor

Post Reply
KenTech
Posts: 33
Joined: 20 Dec 2011, 18:27
Location: Burbank, CA
Contact:

Preventing status collisions

Post by KenTech »

We are using MantisBT 1.2.17 -- we will update soon -- and just ran into a collision issue.
  1. QA #2 was in the process of changing the status of a bug to REVIEWED (custom status).
  2. QA #1 changed the status to CLOSED in the meantime.
  3. QA #2 submitted the status change without realizing that QA #1 was working on it, thus re-opening it to REVIEWED.
My workflow permits only CLOSED bugs being set back to FEEDBACK. Why did the system allow QA #2 to make the change? Doesn't the system check the current status and workflow transitions before actually changing the status?
Post Reply