-
assigned issue to
- changed status to open
The UX for configuring a column to prompt for a value is a little confusing
Issue #77
resolved
I created a new column and set the responsible field to empty. This had the effect of containing all issues that have an empty responsible field in that column. It also has the effect of forcing me to set the responsible field when I drag an issue to that column.
I found this a bit confusing. Perhaps it would be more clear to separate out the columns that are the search criteria for the column vs the fields you want to make mandatory for dragging into that column.
Comments (5)
-
repo owner -
repo owner - changed status to on hold
-
repo owner - changed version to Big Features
-
repo owner - changed version to 0.3
-
repo owner - changed status to resolved
- Log in to comment