Maintenance workspace, to the point?

[Jan van Mastbergen]

In a requirements analysis I am trying to keep track of discussions, questions etc. using the maintenance workspace. Its use bothers me somewhat. It has tabs for todo's, issues, defect, changes. In reality the distinction is not that sharp and something that starts out as an issue may turn into a defect or change request on second thought. Happens all the time but I cannot switch type other than by retyping the issue  in another tab. So rather than separate object types each with their own but very similar data entry screen I would have preferred a selectable issue type code on a single screen.
To my surprise this is how the various issue types are actually implemented in the t_objectproblems table.
Might I ask for a GUI change? It would make life a lot more pleasant when glossing over requirement issues in f.i. an interactive session with customers.

Regards, Jan

[Paolo F Cantoni]

Good idea!

Formally request a feature from Sparx, you can use the [size=13]Request a Feature[/size] link via the Support link at the top of the page.
Place a reference back to this topic in the message.  That way, the Sparxians can see any ongoing discussion.
If you get a response, please add it to the topic.

Paolo

[«Midnight»]

Yes, this really does make sense. An excellent idea for a (hopefully) straightforward enhancement.

David