I have an application called "Redmine-Bugtracker" with the matrix below. This permission matrix allows users to add permitted status-steps on an issue depending on the current-status of it.
So you see on the left side, in the first column of the each row belong to Gegenwärtiger Status --aka current-status. There are all the steps an issue can be in the form of.
In all the columns for the right side under Neue Berechtigungen --aka new-permissions, you see all the steps you can do if the current-status is the one in the leftmost column.
Now what happened is, my colleagues added a new status step as Auftrag unklar --aka assignment/task unclear. So as to mark a ticket where it is unclear what you should do, when the PMs leave you in the unclear what has to be done.
Now what happened is, they set permissions on the row of "Auftrag unklar", thinking it would unlock the issue-status in the tracker. Instead, what the crosses in the pink row defined, is which status-steps are possible when the current-status is "Auftrag unklar". What they would have needed to be doing, is set the crosses in the red-marked column instead.
I was wondering, what is wrong with this UI design, and more to the point, how on earth could this be done better, so as to be less confusing?
How to take some cognitive-load off the user?
I mean, if the programmers can't understand such a matrix, then how could an average user do it?
I'm asking because we have a similar workflow in our application, where the user should do exactly the same as in this example. Configuring (=allowing or disallowing) some status-steps depending on the current-status of some entity.