Jason,
The two attributes you describe seem like different attributes. One for the person creating the ticket (reporting the issue) and one for the person resolving the issue. And it seems like the values of the attributes would be inverse. So it doesn't *seem* like a single attribute to me.
Maybe you could use an enumeration? Values might be Needs Attention and Resolved. This would prevent you having to try to pull a 'boolean switcheroo' which has some risks, imo.
Mike
I guess the most safe solution to these kinds of requirements, without using javascript, is to create a new attribute in a npe helper in combination with change events