When editing a custom field, in this case Assignee, you have the option to
show field conditionally
define a default value via groovy script, in my case the current user
include field on issue open
In my issue workflow newly opened issues do not have an assignee. So show field conditionally and Include field on issue open have been deactivated.
Now I have an issue type called Task and if I create a new issue of type Task I want to ask for an assignee. So I edited the Assignee custom field and activated show field conditionally using rule Type is any of Task and also activated include field on issue open.
However that causes all kinds of unwanted side effects. While the UI when creating a new issue looks the way I want to (it does not ask for assignee unless I choose issue type Task), OneDev always adds the default assignee to the issue, even is the assignee field is not shown in the UI for other issue types. So newly created issues of type Feature are now suddenly automatically assigned to the issue reporter as the groovy script for the default value is executed.
Also in the issue list and issue board the assignee is now always hidden unless the issue is of type Task.
So I reverted the configuration.
I think what OneDev is missing is a condition rule assigned to the include field on issue open open so I can tell OneDev to only ask for the assignee field for specific issue types. If the condition is false it should behave the same as if include field on issue open is deactivated.
jbauerchanged title5 months ago
Previous Value
Current Value
Issue: Include custom field on issue open condionally
Issue: Include custom field on issue open conditionally
Robin Shenchanged state to 'Closed'4 months ago
Previous Value
Current Value
Open
Closed
Robin Shen commented 4 months ago
This is closed as current behavior is by design, and works as expected.
When editing a custom field, in this case
Assignee
, you have the option toIn my issue workflow newly opened issues do not have an assignee. So
show field conditionally
andInclude field on issue open
have been deactivated.Now I have an issue type called
Task
and if I create a new issue of typeTask
I want to ask for an assignee. So I edited theAssignee
custom field and activatedshow field conditionally
using ruleType is any of Task
and also activatedinclude field on issue open
.However that causes all kinds of unwanted side effects. While the UI when creating a new issue looks the way I want to (it does not ask for assignee unless I choose issue type
Task
), OneDev always adds the default assignee to the issue, even is the assignee field is not shown in the UI for other issue types. So newly created issues of typeFeature
are now suddenly automatically assigned to the issue reporter as the groovy script for the default value is executed.Also in the issue list and issue board the assignee is now always hidden unless the issue is of type
Task
.So I reverted the configuration.
I think what OneDev is missing is a condition rule assigned to the
include field on issue open
open so I can tell OneDev to only ask for theassignee
field for specific issue types. If the condition is false it should behave the same as ifinclude field on issue open
is deactivated.