-
-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'@' mentions for users does not work #407
Comments
Hi @integrii, on-premises installation use jira api v2 and it expects the data in this format
Note that you'll need to use display name if its available. If you are unsure about the display name you can check it from But yeah there seem to be some problem with escaping, I will check that. However tagging a user should work for valid input. |
I tried to put [~displayname] into a comment, but it is turned into
|
It seems markdown is not working in the comments. It can work with the following change: index 79e160d..aecdf8c 100644
--- a/pkg/jira/issue.go
+++ b/pkg/jira/issue.go
@@ -274,7 +274,7 @@ type issueCommentRequest struct {
// AddIssueComment adds comment to an issue using POST /issue/{key}/comment endpoint.
func (c *Client) AddIssueComment(key, comment string) error {
- body, err := json.Marshal(&issueCommentRequest{Body: md.ToJiraMD(comment)})
+ body, err := json.Marshal(&issueCommentRequest{Body: comment})
if err != nil {
return err
}``` |
1. Fix ankitpokhrel#407 2. Fix ankitpokhrel#638 3. Display epic on the issue list
It's seems on long ongoing issue, I've the same problem here
Cloud version |
Describe the bug
When I use @user.name, it comes out as plain text in the JIRA UI. When I fetch an issue with an At mentioned member, I see the user prefixed with
/~
, However when I try to also put in/~user.name
it comes out as plain text in the UI and\/~user.name
in myjira-cli
.Please provide following details
To Reproduce
Steps to reproduce the behavior:
jira issue create
@user.name
is plain textExpected behavior
@ mention binds to a user and notifies them as in the JIRA UI.
The text was updated successfully, but these errors were encountered: