Robin Shen opened 2 weeks ago
|
|||||
OneDev changed state to 'Closed' 2 weeks ago
|
|||||
State changed as code fixing the issue is committed (e54ed24f) |
|||||
OneDev changed state to 'Released' 2 weeks ago
|
|||||
State changed as build #5047 (10.6.0) is successful |
|||||
Are existing, possibly older cross project issue references updated when defining a project key? |
|||||
It will not be updated, but the link still works. |
|||||
Thanks for your answer. So old links will break once projects are moved/renamed after a project key has been defined. |
|||||
Yes
|
Type |
Improvement
|
Priority |
Normal
|
Assignee | |
Labels |
No labels
|
Issue Votes (0)
With project key, we can refer to issues something like OD-100. When refer to issues not in current project, using project key instead of project path provides a stable approach even if project is renamed or moved. The issue reference string is also shorter and convenient to use.
Defining project key is optional, and previous approach of referring issues such as
#100
orpath/to/project#100
will also work.This will also work for builds and pull requests.