-
-
Previous Value Current Value Open
Closed
-
@robin Not sure why this was closed because this is definitely not working for me.
Even when I hit Enter for the link, it's not the pasted link that gets added, but rather the first item in the options list.
-
Just input
DevOps/terraform#135here. This is shown in the issue detail page at right side. -
Nevertheless will add a description to make it more explicit.
-
@robin Your suggestion might work perfectly for projects that are native to OneDev.
However, when a project is imported I'm finding PRs that are being named using the short name and then a number that actually conflicts with the issue with the same number.
I mean, I'm not sure if it's because my project is imported or if this is for all projects, but I suspect it 's because it's imported.
Therefore, the only way for me to absolutely know that I've got the correct link is to copy it from the URL on the address bar.
-
... that actually conflicts ...
Just to give you an example, right now I'm up to issues in the 700s. but I'm having PRs that are being created in the 80s.
And both of them are sharing the same short names. Just today, PRs for LAM-80 and LAM-81 were created, which is confusing because I have imported issues that have the same number.
(imported from GitLab)
-
Issues and PRs in OneDev are numbered independently. Issue can only link to issues, not PRs.
-
I think mixing them in same number space is actually confusing, as they are really different things (issues are requirements/specs, and PRs are implementations)
-
PS: when referencing PRs in markdown, one has to write
pr #<number> -
-
Previous Value Current Value Closed
Open
-
On behalf of AI user "Service Desk": Failed to do the job, please open workspace OD-3 for details
-
@servicedesk please try again
-
@zaakiy Yes, that's correct. To reference a PR in a child project in Markdown, use:
pr DevOps/terraform#135Or alternatively with the full phrase:
pull request DevOps/terraform#135Both formats will create a link to the PR in the specified project.
-
Previous Value Current Value Open
Closed
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Summary
When adding an issue link via Select Existing, allow pasting a full issue URL (including cross-project URLs) so the target issue is resolved and linked.
Current behavior
The issue picker accepts:
project/path#<number-or-query>or<project-key>-<number-or-query>It does not accept a full issue URL such as:
https://<host>/<project/path>/~issues/<number>Pasting such a URL fails to resolve the issue, which is especially awkward for cross-project links where the URL is what users typically copy from the browser.
Expected behavior
When the user pastes an issue URL into the link picker:
Acceptance criteria
project#/KEY-input continues to workRelated question: #2891