What's the type of a test? Maybe it shoudl be clarified in the user interface, or if there is just one of them, hide it. Additionally, when adding a test, if the status is hard-coded, then hide it, don't disable it
What's the type of a test? Maybe it shoudl be clarified in the user interface, or if there is just one of them, hide it. Additionally, when adding a test, if the status is hard-coded, then hide it, don't disable it
Comments
Comment #1
Bojhan commentedThe type is now Task completion, we should indeed add something to the UI to clarify what the test does.
Agreed, on hiding status.
Comment #2
boombatower commentedI've debated were to place additional help text, could simply put it on the node form, but assuming there will eventually be a number of options with somewhat detailed descriptions I haven't gotten to it. (documentation is the last item on schedule, been waiting for interface to be confirmed before documenting it)
Since it is the only option right now, shouldn't be a big deal.
The status isn't "hard-coded" per say. You just can't select either of the other two states on creation. Since it displays later I think it creates an inconsistent interface, but obviously it can be done.
Comment #3
boombatower commentedThis is part of #320222: Create a study/task workflow and the status field is hidden.