Skip to content
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

Support case where issue reporter is blank for new issue creation event #1032

Closed
mickmister opened this issue Mar 12, 2024 · 2 comments · Fixed by #1033
Closed

Support case where issue reporter is blank for new issue creation event #1032

mickmister opened this issue Mar 12, 2024 · 2 comments · Fixed by #1033
Assignees
Labels
Type/Bug Something isn't working
Milestone

Comments

@mickmister
Copy link
Contributor

mickmister commented Mar 12, 2024

An issue is occurring when no Reporter field is present on a newly created issue. According to the customer, the reporter field is hidden in the field setting scheme in JIRA. The issue is happening here:

avatarLink := fmt.Sprintf("![avatar](%s =30x30)", issue.Fields.Reporter.AvatarUrls.One6X16)

We'll also want to make sure we are defensive with other instances of the Reporter field, as possibly look into other potential cases of missing fields in the codebase.

Issue created from a Mattermost message by @hanzei.

@hanzei hanzei added the Type/Bug Something isn't working label Mar 12, 2024
@hanzei hanzei self-assigned this Mar 13, 2024
@hanzei hanzei added this to the v4.1.1 milestone Mar 13, 2024
@raghavaggarwal2308
Copy link
Contributor

@hanzei @mickmister Just for clarification:

  • On what action the issue is being caused? Is the user trying to create an issue using the MM interface?

@hanzei
Copy link
Collaborator

hanzei commented Mar 13, 2024

@raghavaggarwal2308 Yes, the bug happens when a user creates an issue via the MM UI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type/Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants