|
Stanislav N. opened 1 year ago
|
||||||
|
This is not a bug. Fixing commits tab only references commits stated to fix the issue. A simple issue reference will not affect that. I think that adding a separate tab to show all commits referencing the issue might not be of too much value, but make the issue tab a bit confusing (you have fixing commits, related commits, etc). |
||||||
|
|
Then maybe a github/gitlab-like approach? Adding a comment from OneDev user like field change, but with text like: Sometimes one commit might be related to more than one issue and copy-paste commit hash to every issue is time-consuming. |
||||||
|
|
Robin Shen changed fields 1 year ago
|
||||||
|
|
This seems like a good idea. |
||||||
|
|
Robin Shen changed fields 1 year ago
|
||||||
|
OneDev changed state to 'Closed' 1 year ago
|
||||||
|
|
State changed as code fixing the issue is committed |
||||||
|
|
OneDev changed state to 'Released' 1 year ago
|
||||||
|
|
State changed as build #3440 is successful |
||||||
|
Referenced from commit 1 year ago
|
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee |
This could be a continuation of issue #795.
I've tried to specify issue in commits in different forms, e.g.:
Related to issue #IDRef: issue #IDissue #ID(including different casing)Yet none of them actually connects commit to issue, there is no message in issue or separate tab. When referencing issue from commits I expect that somehow this commit appears in issue (separate tab like "Fixing commits" or "Fixing build", or as message like "Commit [hash here] referenced this issue").