search

mattermost / mattermost-plugin-jira

JIRA plugin for Mattermost 🔌
https://mattermost.gitbook.io/plugin-jira/
Apache License 2.0
98 stars 127 forks source link

Reporter is not automatically set for `/jira create` on Jira Cloud, when required field is missing #481

Open DHaussermann opened 4 years ago

DHaussermann commented 4 years ago

On Jira Cloud, when additional custom fields must be set to save a Jira issue the reporter is not being set automatically.

The behaviour where reporter is not show on the creation screen can be changed based on the field configuration and screens configuration.

On the instance I'm testing with this field is visible before the issue is created and the reporter field can be manually adjusted. With this configuration in place, the reported will be automatically set to the current user when creating from within Jira but not when the user is sent over by a link provided by the integration.

A recent PR has solved the issue for Jira Server (https://github.com/mattermost/mattermost-plugin-jira/pull/462) but, Jira Cloud still has the issue.

levb commented 4 years ago

Should this issue be closed? @jfrerich @hanzei are we not properly setup to have issues closed when PRs are merged? Or does it require a specific ("fixes XXX") formatting in the PR?

jfrerich commented 4 years ago

@levb, this ticket should remain open. The merged ticket resolved the issue on server, but it was decided in the merged PR discussion to create a separate issue for resolving in cloud.

Kshitij-Katiyar commented 1 month ago

@DHaussermann @jfrerich @wiggin77 I have investigated the issue and would like to share my findings:

  1. When attempting to create an issue in a project with required fields not supported by our create issue modal, we receive a link to create the issue manually. Opening the link reveals that some fields provided in the create issue modal are prefilled in the form. However, not all provided fields are prefilled. For the cloud server, the reporter field is not prefilled.

  2. I attempted to address the issue but was unsuccessful due to insufficient data received from Jira during issue creation. Specifically, the reporter's username is unavailable, which hampers the automatic population of the reporter field.