Able to specify project key and refer to issues by project key (OD-1883)

Robin Shen opened 2 years ago

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 or path/to/project#100 will also work.

This will also work for builds and pull requests.

OneDev changed state to 'Closed' 2 years ago
Previous Value Current Value
Open

Closed
OneDev commented 2 years ago

State changed as code fixing the issue is committed (e54ed24f)
OneDev changed state to 'Released' 2 years ago
Previous Value Current Value
Closed

Released
OneDev commented 2 years ago

State changed as build #5047 is successful
jbauer commented 2 years ago

Are existing, possibly older cross project issue references updated when defining a project key?
Robin Shen commented 2 years ago

It will not be updated, but the link still works.
jbauer commented 2 years ago

Thanks for your answer. So old links will break once projects are moved/renamed after a project key has been defined.
Robin Shen commented 2 years ago

Yes

On May 6, 2024, at 19:51, Robin Shen <[email protected]> wrote:

jbauer commented

Thanks for your answer. So old links will break once projects are moved/renamed after a project key has been defined.

Reply this email to post comment, or click this link for details

You received this as you are participating in this topic. Mail to this address to unsubscribe
wojtek referenced from other issue 2 years ago

Cross-project issues best practise (OD-1909)

Closed
Login to comment

Previous Value	Current Value
Open	Closed

Previous Value	Current Value
Closed	Released

Type	Improvement
Priority	Normal
Assignee	Robin Shen
Labels	No labels

Issue Votes (0)

Watchers (3)

Reference

OD-1883