|
Michael Weimann opened 4 years ago
|
||||
|
@robin I can take this one as it is very urgent for me. That would be my plan:
Are there any other places? |
||||
![]() |
This is all of the place I can think of right now. |
||||
|
@robin I started working on this. I have a question: How can I make the checkbox appear in the project settings. In my opinion the actual setting should be stored in ProjectIssueSetting. It looks like the form fields are generated based on annotations inside the model and the properties list here. Can I just add a new field to the form? Or should I set the issue settings by delegating methods in |
||||
![]() |
I think putting the setting directly into project class is appropriate. As ProjectIssueSetting contains all issue specific settings after when it is enabled. |
||||
![]() |
Also make sure that:
|
||||
![]() |
OneDev changed state to 'Closed' 4 years ago
|
||||
|
@robin could you please set the milestone for this issue? |
||||
![]() |
Robin Shen changed iterations 4 years ago
|
||||
![]() |
OneDev changed state to 'Released' 4 years ago
|
||||
Referenced from commit 1 day ago
|
For some projects I don't want to have an issue tracking.
This could be the case if I use another project as "issue aggregator" or an external tool.
Just telling people "You opened the issue in the wrong project (again)." does not work in the long run.
Users do not understand it and get frustrated.