Maniphest - Is it possible to have only single user validation on a custom "users" field
Maniphest - Is it possible to have only single user validation on a custom "users" field
Event Timeline
kristo.mario updated the question from to Maniphest - Is it possible to have only single user validation on a custom "users" field.Sep 6 2016, 2:39 PM2016-09-06 14:39:33 (UTC+0)
kristo.mario updated the question details. (Show Details)Sep 6 2016, 2:51 PM2016-09-06 14:51:56 (UTC+0)
jonathanrseawright added a subscriber: jonathanrseawright.Edited · Sep 11 2016, 12:32 AM2016-09-11 00:32:14 (UTC+0)
Comment ActionsAs far as I can tell (I'm not a contributor), restricting the 'users' field to a single user isn't supported. Is there any reason your team could just put one user in the box? It sounds to me like it would support your workflow as-is.
My suggestion
I'd consider adding multiple fields like the one you described. One for each:
- assigned tester
- assigned engineer
Let the assigned to field designate who is actively responsible for the task at the moment.
If you need users to be able to view tasks that are sent back from the QA team, a few approaches come to mind:
- Add special statuses for these tasks (QA - Rejected, QA - More Info)
- You could then setup a herald rule for your team that triggers on these statuses
- Use multiple user fields, and then build dashboard pages for each team showing tasks that have been recently kicked back (open status, and "engineer" != "".). You can do this using queries.