-
Previous Value Current Value Issue: Include custom field on issue open condionally
Issue: Include custom field on issue open conditionally
-
Previous Value Current Value Open
Closed
-
This is closed as current behavior is by design, and works as expected.
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
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 conditionallyandInclude field on issue openhave been deactivated.Now I have an issue type called
Taskand if I create a new issue of typeTaskI want to ask for an assignee. So I edited theAssigneecustom field and activatedshow field conditionallyusing ruleType is any of Taskand 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 typeFeatureare 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 openopen so I can tell OneDev to only ask for theassigneefield for specific issue types. If the condition is false it should behave the same as ifinclude field on issue openis deactivated.