-
This is a documentation mistake. State transitions per project is not implemented yet. Changed issue type to improvement.
-
Name Previous Value Current Value Type
Bug
Improvement
-
Previous Value Current Value No way to override issue transitions per-project while admin panel says it's possible
Able to override issue state transition rules at project level
-
Previous Value Current Value Open
Closed
-
Specify issue transition rule for certain projects is actually possible. This can done by adding a project criteria to applicable issues setting of the rule.
-
Hm, yes, you're right. Yet it is counterintuitive (otherwise this issue won't be created at all) and docstrong in state management interface misleads.
I think there are two ways to go:
- Fix docstring on top of issue's state management that do not add misunderstandings and mention that project should be defined in "Applicable issues" field.
- Add state management UI in project's settings.
-
Thanks. Will add necessary documents on that. The way of using applicable issues is much flexible and concept consistent, and it allows configuring state transition not only based on projects, but also based on any custom field values, and they all conveyed via OneDev's issue query.
-
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee |
Issue Votes (0)
When looking in Administration -> Issue Setting -> State Transitions I saw:
But in project's settings there are no ability to do that - there are no settings about issues, I can only enable or disable them.