onedev/server

#939 State Transitions: 'Code committed' does not work across projects?

Closed

Activities

jbauer opened 2 years ago

I have configured an issue state transition to committed state when code is committed to branches master, main, dev. This works well within the project, however a commit in project-a with message Resolves issue company/group/project-b#1 Some Text does not seem to trigger the state transition for issue #1 in project-b.

Is that expected behavior?

Robin Shen commented 2 years ago

It only works if project-a is ancestor of project-b or vice versa. This is by design for performance reason.

Robin Shen commented 2 years ago

Another reason is for security consideration. Person with permission to push repository can fix issues in the whole hierarchy, but not for unrelated projects.

jbauer commented 2 years ago

Hmm I see. Unfortunately in my case project-a and project-b are sibling projects however they share a common ancestor.

company
|--- apps
     |--- project-a
|--- other
     |--- project-b

Developers have code write access on everything below company. Non-developers have only read access to selected leaf projects. So I thought that automatic issue closing should work.

Robin Shen changed state to 'Closed' 2 years ago

Previous Value	Current Value
Open	Closed

Type	Question
Priority	Normal
Assignee	Robin Shen

Issue Votes (0)

Watchers (3)

Reference

onedev/server#939