|
empinator opened 2 weeks ago
|
||||
|
|
So, I guess I found a way by naming the referenced (parent-)project as a prefix to the issue id, like "onedev#1234" Is that the only way or can I define a default? |
||||
|
As you've discovered, project path needs to be prefixed before issue number to reference isssues in other projects to avoid potential conflicts and confusions. |
||||
|
|
thank you very much for your reply. I guess it makes sense then to force a prefix with a commit comment through a pre-commit hook. thanks again. |
||||
|
|
empinator changed state to 'Closed' 2 weeks ago
|
| Type |
Question
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Watchers (3)
Hi there,
our setup consists of various artifacts which are developed within child projects which all contribute to the shippable product. Since everything follows one roadmap we only have one issue management on the parent project.
However, if I commit something within the child-project with a comment referencing an issue from the parent, no activity is added to the issue. Clicking on an issue number on a file's last commit comment within leads to a 404, since it's looking for the issue inside the child project.
I did find this particular ticket seeming to relate to the same issue: #695 But I can't figure out how to set up the project(s) in order work that way.
Am I doing something wrong or is this feature simply not working?
If this is not working at the point I was wondering if this feature is planned in the near future, by having an extra setting to either say "use parent project's issue management: true/false" or, even better, "use issue management of this project: "? Looking foward to your reply, best - e