-
Suggestion
-
Resolution: Timed out
-
2
-
Issue Summary
When mentioning an issue key in pull request description, this is also triggering workflow triggers and transitioning issues. Sometimes the issues mentioned in the pull-request description are not the origin the work, but only vaguely related. For example, a pull request description of "Fix for potential NPE found after releasing TEST-123".
Steps to Reproduce
- Apply a workflow trigger to any transition in a JSW project
- Mention an issue key in pull request description in GitHub
Expected Results
The mention of an issue key in pull request description should only link Jira issues, but not trigger Jira issue transitions whenever workflow triggers are configured.
Actual Results
Whenever an issue key is added to a pull request description, it also triggers transition if workflow triggers are configured.
Workaround
Instead of using a proper issue key like `TEST-123` when referring to unrelated work, you can refer to it with another separator than `-`. As in, `TEST 123` instead of `TEST-123`.
[JRACLOUD-90018] Don't transition issue keys found in pull request descriptions
This repros for us even when the issue key appears only in the URL of a hyperlink (i.e., not the display text).
Example: a PR description includes a line like "eventually we will replace this with a call to an external service" (in GitHub markdown syntax: [an external service](https://example.atlassian.net/browse/TEST-123)) where the URL is what you get from Jira's "copy link to issue" functionality, which includes the issue key as a substring (e.g.,`TEST-123`). The intent is for PR reviewers to be able to quickly access additional details about related work that is still in progress or scheduled for the future, to put the current code change in context.
The workaround listed here would require PR reviewers to see the string "TEST 123", open Jira in a separate tab, and search for that issue key or construct the URL themselves. That's pretty burdensome. Unless there's a way of linking to a Jira issue without mentioning the issue key (and without using some kind of URL shortener)–if so, we'd be interested to know the details!
Hi everyone,
Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team - Jira Cloud Product Management